On Mon, 2014-01-20 at 18:30 +, Varun Sethi wrote:
>
> > -Original Message-
> > From: Alex Williamson [mailto:alex.william...@redhat.com]
> > Sent: Monday, January 20, 2014 9:51 PM
> > To: Sethi Varun-B16395
> > Cc: io...@lists.linux-foundation.org; linux-kernel@vger.kernel.org
> > Subj
On Monday 20 January 2014, Srikanth Thokala wrote:
> >
> >> > * data width should be a property of the slave driver that is configured
> >> > through dma_slave_config(), unless you can have dma engines that only
> >> > support certain a width.
> >>
> >> Yes, this VDMA engine soft IP support onl
On Monday 20 January 2014, Hanjun Guo wrote:
> >> acpi_register_ioapic()/acpi_unregister_ioapic() will be used for IOAPIC
> >> hotplug and GIC distributor is something like IOAPIC on x86, so I think
> >> these two functions can be reserved for future use.
> > But GIC is not hotplugged, is it? It st
On Mon 20-01-14 11:15:09, Michal Hocko wrote:
> On Wed 15-01-14 20:13:04, Alan Ott wrote:
> [...]
> > 2. __copy_to_user_memcpy() takes a read lock (down_read()) on
>
> This looks like a bug. copy_to_user_* shouldn't take mmap_sem at all
> Check the might_fault annotation used in generic code. Arm
On 01/20/2014 11:52 AM, Peter Zijlstra wrote:
> On Fri, Jan 17, 2014 at 04:12:06PM -0500, r...@redhat.com wrote:
>> +++ b/kernel/sched/fair.c
>> @@ -1300,10 +1300,14 @@ static void update_numa_active_node_mask(struct
>> task_struct *p)
>> faults = numa_group->faults_from[task_faults_
On 01/20, Alan Stern wrote:
>
> On Mon, 20 Jan 2014, Oleg Nesterov wrote:
>
> > On 01/17, Alan Stern wrote:
> > >
> > > Also, take a look at commit 356c05d58af0. It's a similar situation
> > > (not exactly the same).
> >
> > At first glance, can't __ATTR_IGNORE_LOCKDEP() use no_validate too ?
> >
Linus,
for 3.14, the I2C subsystem has the following to offer:
* new drivers for Renesas RIIC and RobotFuzz OSIF
* driver cleanups & improvements & bugfixes
Pretty standard stuff this time, I'd say. There is more complex stuff
coming up, but I didn't have the bandwidth between the years to pull
On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
> On 20 January 2014 19:17, Nicolas Pitre wrote:
> > On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
> >> Calling getauxval(AT_HWCAP) on an outdated libc.so will give you the
> >> whole value, not just the bits whose meaning was known to glibc at the
> >> tim
kbuild, 0day kernel build service, outputs the warning:
arch/x86/kernel/irq.c:333:1: warning: the frame size of 2056 bytes
is larger than 2048 bytes [-Wframe-larger-than=]
because check_irq_vectors_for_cpu_disable() allocates two cpumasks on the
stack. Fix this by using cpumask_var_t, the cpumas
Hi David,
thanks for the review
On Sat, Jan 18, 2014 at 5:51 AM, David Herrmann wrote:
> Hi
>
> On Fri, Jan 17, 2014 at 8:12 PM, Benjamin Tissoires
> wrote:
>> Evemu [1] uses uinput to replay devices traces it has recorded. However,
>> the way evemu uses uinput is slightly different from how ui
On 20 January 2014 19:55, Nicolas Pitre wrote:
> On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
>
>> On 20 January 2014 19:17, Nicolas Pitre wrote:
>> > On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
>> >> Calling getauxval(AT_HWCAP) on an outdated libc.so will give you the
>> >> whole value, not just th
On 20/01/14 18:33, Luis R. Rodriguez wrote:
> On Mon, Jan 20, 2014 at 2:38 AM, David Vrabel wrote:
>> On 17/01/14 23:02, Luis R. Rodriguez wrote:
>>> As per linux-next Next/Trees [0], and a recent January MAINTAINERS patch [1]
>>> from David one of the xen development kernel git trees to track is
On 01/20/2014 11:57 AM, Peter Zijlstra wrote:
> On Fri, Jan 17, 2014 at 04:12:08PM -0500, r...@redhat.com wrote:
>> diff --git a/include/linux/sched.h b/include/linux/sched.h
>> index 0af6c1a..52de567 100644
>> --- a/include/linux/sched.h
>> +++ b/include/linux/sched.h
>> @@ -1471,6 +1471,8 @@ stru
On Mon, 20 Jan 2014 17:52:05 +0100
Peter Zijlstra wrote:
> On Fri, Jan 17, 2014 at 04:12:06PM -0500, r...@redhat.com wrote:
> > From: Rik van Riel
> >
> > +++ b/kernel/sched/fair.c
> > @@ -1300,10 +1300,14 @@ static void update_numa_active_node_mask(struct
> > task_struct *p)
> >
Em Fri, Jan 17, 2014 at 04:34:06PM +0100, Stephane Eranian escreveu:
> This patch fixes a memory corruption problem with the xyarray when
> the evsel fds get closed at the end of the run_perf_stat() call.
>
> It could be triggered with:
> # perf stat -a -e power/energy-cores/ ls
> When cpumask
The grant mapping API does m2p_override unnecessarily: only gntdev needs it,
for blkback and future netback patches it just cause a lock contention, as
those pages never go to userspace. Therefore this series does the following:
- the original functions were renamed to __gnttab_[un]map_refs, with a
On Mon, Jan 20, 2014 at 02:02:32PM -0500, Rik van Riel wrote:
> That is what I started out with, and the results were not
> as stable as with this calculation.
>
> Having said that, I did that before I came up with patch 7/7,
> so maybe the effect would no longer be as pronounced any more
> as it
On Mon, 2014-01-20 at 14:58 +0100, Peter Zijlstra wrote:
> On Thu, Jan 16, 2014 at 04:08:20PM -0800, Tim Chen wrote:
> > Remove unnecessary operation and make the cmpxchg(lock, node, NULL) == node
> > check in mcs_spin_unlock() likely() as it is likely that a race did not
> > occur
> > most of the
On Mon 2014-01-20 18:03:22, Catalin Marinas wrote:
> On Mon, Jan 20, 2014 at 05:47:45PM +, Pavel Machek wrote:
> > On Mon 2014-01-20 17:17:52, Catalin Marinas wrote:
> > > On Mon, Jan 20, 2014 at 05:10:29PM +, Catalin Marinas wrote:
> > > > On Mon, Jan 20, 2014 at 04:49:26PM +, Pavel Ma
On 14-01-20 12:16 AM, Linus Walleij wrote:
On Sat, Jan 18, 2014 at 3:56 AM, Matt Porter wrote:
I wonder if Linus would accept a rename at this point (too late for 3.14
presumably, but for 3.15) of s/capri/bcm281xx throughout, bcm11351 for
the compatible string, as we have for the machine compa
Hi,
Please consider pulling the following patches,
Steve.
The following changes since commit 7a262d2ed9fa42fad8c4f243f8025580b58cf2f6:
Merge git://git.kernel.org/pub/scm/virt/kvm/kvm (2014-01-02 14:50:18 -0800)
are available in
On Tue, Jan 07, 2014 at 11:19:56PM +, Eunbong Song wrote:
>
> panic_nand_wait_ready() and nand_wait_ready() calls dev_ready() without
> checking if it exists.
There are many occasions where we call a function pointer without
(locally) checking that it is non-NULL. That is by design.
If you
The current automatic NUMA balancing code base has issues with
workloads that do not fit on one NUMA load. Page migration is
slowed down, but memory distribution between the nodes where
the workload runs is essentially random, often resulting in a
suboptimal amount of memory bandwidth being availab
From: Rik van Riel
The faults_from statistics are used to maintain an active_nodes nodemask
per numa_group. This allows us to be smarter about when to do numa migrations.
Cc: Peter Zijlstra
Cc: Mel Gorman
Cc: Ingo Molnar
Cc: Chegu Vinod
Signed-off-by: Rik van Riel
---
kernel/sched/fair.c |
From: Rik van Riel
The current code in task_numa_placement calculates the difference
between the old and the new value, but also temporarily stores half
of the old value in the per-process variables.
The NUMA balancing code looks at those per-process variables, and
having other tasks temporarily
From: Rik van Riel
Use the active_nodes nodemask to make smarter decisions on NUMA migrations.
In order to maximize performance of workloads that do not fit in one NUMA
node, we want to satisfy the following criteria:
1) keep private memory local to each thread
2) avoid excessive NUMA migration
From: Rik van Riel
Excessive migration of pages can hurt the performance of workloads
that span multiple NUMA nodes. However, it turns out that the
p->numa_migrate_deferred knob is a really big hammer, which does
reduce migration rates, but does not actually help performance.
Now that the secon
From: Rik van Riel
Track which nodes NUMA faults are triggered from, in other words
the CPUs on which the NUMA faults happened. This uses a similar
mechanism to what is used to track the memory involved in numa faults.
The next patches use this to build up a bitmap of which nodes a
workload is a
From: Rik van Riel
The tracepoint has made it abundantly clear that the naive
implementation of the faults_from code has issues.
Specifically, the garbage collector in some workloads will
access orders of magnitudes more memory than the threads
that do all the active work. This resulted in the n
On Mon, 2014-01-20 at 13:07 +0100, Peter Zijlstra wrote:
> On Thu, Jan 16, 2014 at 04:08:16PM -0800, Tim Chen wrote:
> > +/*
> > + * We don't inline mcs_spin_lock() so that perf can correctly account for
> > the
> > + * time spent in this lock function.
> > + */
> > +static noinline
> > +void mcs_
Hi Markus,
I'm the xHCI driver maintainer, and it helps to Cc me on USB 3.0 bug
reports.
On Sat, Dec 28, 2013 at 07:24:20AM +0100, Markus Rechberger wrote:
> just received following log snippset:
Please state which kernel version you (or your customer) is running.
You've reported issues with sev
This fixes a build failure that seems to be present since commit
commit b81f18e55e9f4ea81759bcb00fea295de679bbe8
Author: Tony Breeds
Date: Tue Apr 3 15:00:39 2012 +
powerpc/boot: Only build board support files when required.
This is easily reproducible my using the ep88xc_defconfig co
On 01/20/2014 11:31 AM, Peter Zijlstra wrote:
> On Fri, Jan 17, 2014 at 04:12:05PM -0500, r...@redhat.com wrote:
>> /*
>> + * Iterate over the nodes from which NUMA hinting faults were triggered, in
>> + * other words where the CPUs that incurred NUMA hinting faults are. The
>> + * bitmask is used
This fixes a build failure that seems to be present since commit
commit b81f18e55e9f4ea81759bcb00fea295de679bbe8
Author: Tony Breeds
Date: Tue Apr 3 15:00:39 2012 +
powerpc/boot: Only build board support files when required.
This is easily reproducible my using the storcenter_defconfi
On Wed, Jan 08, 2014 at 08:58:49AM +0900, Jingoo Han wrote:
> On Tuesday, January 07, 2014 10:39 PM, Wei Yongjun wrote:
> >
> > From: Wei Yongjun
> >
> > Remove unneeded error handling on the result of a call
> > to platform_get_resource() when the value is passed to
> > devm_ioremap_resource().
Commit-ID: 741e3902cd89a7fbc04ae53f29a7ca0da452aa8e
Gitweb: http://git.kernel.org/tip/741e3902cd89a7fbc04ae53f29a7ca0da452aa8e
Author: Ingo Molnar
AuthorDate: Mon, 20 Jan 2014 19:51:05 +0100
Committer: Ingo Molnar
CommitDate: Mon, 20 Jan 2014 19:57:39 +0100
x86/intel/mpx: Remove unused
When CONFIG_MPIC_WEIRD is defined, the following build error occurs:
arch/powerpc/sysdev/mpic.c: In function 'mpic_set_irq_type':
arch/powerpc/sysdev/mpic.c:892:9: error: case label does not reduce to an
integer constant
MPIC_INFO(VECPRI_POLARITY_POSITIVE):
^
arch/powerpc/sysdev
On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
> On 20 January 2014 19:55, Nicolas Pitre wrote:
> > On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
> >
> >> On 20 January 2014 19:17, Nicolas Pitre wrote:
> >> > On Mon, 20 Jan 2014, Ard Biesheuvel wrote:
> >> >> Calling getauxval(AT_HWCAP) on an outdated
The MPC7448HPC2 and PPC_HOLLY config options contain TSI108_BRIDGE
duplicates since commit:
commit 3490cba56f7f8a78ef4c94814c3181f09ce1e2ef
Author: Jon Loeliger
Date: Wed Jan 23 12:42:50 2008 -0600
[POWERPC] Add initial iomega StorCenter board port.
This patch cleans these duplicates.
Si
On Sat, Jan 18, 2014 at 3:31 AM, Dorau, Lukasz wrote:
> On Friday, January 17, 2014 10:44 PM Alexei Starovoitov
> wrote:
>> On Fri, Jan 17, 2014 at 1:02 PM, Markus Trippelsdorf
>> wrote:
>> > On 2014.01.17 at 11:58 -0800, Alexei Starovoitov wrote:
>> >> On Fri, Jan 17, 2014 at 9:58 AM, Alexei S
On Fri, Jan 17, 2014 at 01:20:36PM +0530, Prabhakar Lad wrote:
> On Fri, Jan 17, 2014 at 10:46 AM, Prabhakar Lad
> wrote:
> > On Fri, Jan 17, 2014 at 3:02 AM, Brian Norris
> > wrote:
> >> On Wed, Jan 15, 2014 at 01:38:26PM +0530, Prabhakar Lad wrote:
> >>> From: "Lad, Prabhakar"
> >>>
> >>> This
Hi Linus,
This includes the basic infrastructure for MPX (Memory Protection
Extensions) support, but does not include MPX support itself. It is,
however, a prerequisite for KVM support for MPX, which I believe will
be pushed later this merge window by the KVM team.
This includes moving the funct
I'm sorry for this. Looks like I still had problems with some whitespaces. I
will resend the patch and hope, it will work now.
Daniel
Am 17.01.2014 um 13:22 schrieb Mark Brown :
> On Tue, Jan 14, 2014 at 08:34:10PM +0100, Daniel Matuschek wrote:
>
>> WM8804 can run with PLL frequencies of 256x
On Sun, Jan 19, 2014 at 01:49:57AM +0200, Kirill A. Shutemov wrote:
> __khugepaged_enter() has VM_BUG_ON(khugepaged_test_exit(mm)).
> Do we really want to crash there if MMF_THP_DISABLE is set?
No, definitely not. Upon review, khugepaged_test_exit is the wrong
place to do this check. I think I n
WM8804 can run with PLL frequencies of 256xfs and 128xfs for
most sample rates. At 192kHz only 128xfs is supported. The
existing driver selects 128xfs automatically for some lower
samples rates. By using an additional mclk_div divider, it
is now possible to control the behaviour. This allows usin
On 01/20, Alex Thorlton wrote:
>
> No, definitely not. Upon review, khugepaged_test_exit is the wrong
> place to do this check. I think I need to move it up to
> khugepaged_scan_mm_slot for this to work correctly.
Why? unless a MMF_THP_DISABLE task does madvise(MADV_HUGEPAGE)
khugepaged_scan_mm_
Ping? Benoit can you please merge this trivial update. Thanks.
On Sat, Dec 21, 2013 at 4:12 PM, Marek Belisko wrote:
> BMP085 EOC (End Of Conversion) irq line is connected to
> gpio113 on gta04. Set irq properties to have driver using irq
> instead polling for EOC.
>
> Signed-off-by: Marek Belisk
On Mon, Jan 20, 2014 at 09:15:25PM +0100, Oleg Nesterov wrote:
> On 01/20, Alex Thorlton wrote:
> >
> > No, definitely not. Upon review, khugepaged_test_exit is the wrong
> > place to do this check. I think I need to move it up to
> > khugepaged_scan_mm_slot for this to work correctly.
>
> Why?
I am announcing the release of the Linux 3.8.13.16 kernel.
The updated 3.8.y tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.8.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.8.y;a=shortlog
The diff from v3.8.13.15 is post
Hi!
> > > Race to idle doesn't mean that the screen goes off as well. Let's say
> > > the screen stays on for 1 min and the CPU needs to be running for 10s
> > > over this minute, in the first case you have:
> >
> > No, it does not. I just assumed user is continuing to use his
> > machine. Obviou
From: Fabio Estevam
'lay' is not very meaningful, so use it 'layer' instead to let the dev_info()
clearer.
Signed-off-by: Fabio Estevam
---
drivers/regulator/pfuze100-regulator.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/regulator/pfuze100-regulator.c
b/drive
The following changes since commit 802eee95bde72fd0cd0f3a5b2098375a487d1eda:
Linux 3.13-rc6 (2013-12-29 16:01:33 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/
tags/char-misc-3.14-rc1
for you to fetch changes up to 6adb8ef
The following changes since commit 413541dd66d51f791a0b169d9b9014e4f56be13c:
Linux 3.13-rc5 (2013-12-22 13:08:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core.git/
tags/driver-core-3.14-rc1
for you to fetch changes up to db4
The following changes since commit 413541dd66d51f791a0b169d9b9014e4f56be13c:
Linux 3.13-rc5 (2013-12-22 13:08:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty.git/
tags/tty-3.14-rc1
for you to fetch changes up to 8bc661bfc0c2d221e20
The following changes since commit 413541dd66d51f791a0b169d9b9014e4f56be13c:
Linux 3.13-rc5 (2013-12-22 13:08:32 -0800)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/
tags/usb-3.14-rc1
for you to fetch changes up to 2fc5a7dace3c43e6240
I made a quick and dirty sparse patch to check for this. I don't think
I will bother trying to send it to sparse upstream, but you can if you
want to.
It found 289 unions which might need a __packed added. The lustre
unions were not in my allmodconfig so they're not listed.
Perhaps there could
On Mon, Jan 20, 2014 at 10:05:30AM +, Russell King - ARM Linux wrote:
> On Mon, Jan 20, 2014 at 02:32:34PM +0530, Tushar Behera wrote:
> > uart_register_driver call binds the driver to a specific device
> > node through tty_register_driver call. This should typically happen
> > during device pr
On Mon, Jan 20, 2014 at 04:55:52PM +0800, Roger wrote:
> On 01/16/2014 05:35 PM, Lee Jones wrote:
> +static int rtsx_usb_bulk_transfer_sglist(struct rtsx_ucr *ucr,
> + unsigned int pipe, struct scatterlist *sg, int num_sg,
> + unsigned int length, unsigned int *a
Hi!
> Another problem is that I don't know any other systems supporting charge
> thresholds, and I don't want to dictate interfaces built for ThinkPads
> as a generic way.
On systems like Sharp Zaurus, Nokia N900, charging is controlled by
Linux. As charge thresholds should extend Li-ION battery
When in compat mode, load and parse the dwarf debug info accordingly.
Tested dwarf local unwinding on ARMv8 (aka AARCH64) with ARMv7 and
ARMv8 binaries.
Signed-off-by: Jean Pihet
---
src/dwarf/Gfde.c| 25 --
src/dwarf/Gfind_proc_info-lsb.c | 194
When in compat mode, correctly unwind the recorded stack frame. The
returned pointers are cast to the desired target address size.
Signed-off-by: Jean Pihet
---
src/dwarf/Gparser.c | 27 +++
1 file changed, 27 insertions(+)
diff --git a/src/dwarf/Gparser.c b/src/dwarf/Gp
In the case of unwinding the debug info from a binary that has a different
address size than the current native platform, it is needed to record
it in the address space struct, in order to correctly parse the debug
info later. This mode is known as compat mode.
This is the case on e.g. profiling a
In the case of unwinding the debug info from a binary that has a different
address size than the current native platform, it is needed to record
it in the address space struct, in order to correctly parse the debug
info later. This mode is known as compat mode.
This is the case when e.g. profiling
A long known problem of the upstream netback implementation that on the TX
path (from guest to Dom0) it copies the whole packet from guest memory into
Dom0. That simply became a bottleneck with 10Gb NICs, and generally it's a
huge perfomance penalty. The classic kernel version of netback used grant
This patch contains the new definitions necessary for grant mapping.
v2:
- move unmapping to separate thread. The NAPI instance has to be scheduled
even from thread context, which can cause huge delays
- that causes unfortunately bigger struct xenvif
- store grant handle after checking validity
A malicious or buggy guest can leave its queue filled indefinitely, in which
case qdisc start to queue packets for that VIF. If those packets came from an
another guest, it can block its slots and prevent shutdown. To avoid that, we
make sure the queue is drained in every 10 seconds.
The QDisc queu
These counters help determine how often the buffers had to be copied. Also
they help find out if packets are leaked, as if "sent != success + fail",
there are probably packets never freed up properly.
Signed-off-by: Zoltan Kiss
---
drivers/net/xen-netback/common.h|3 +++
drivers/net/xen-
Unmapping causes TLB flushing, therefore we should make it in the largest
possible batches. However we shouldn't starve the guest for too long. So if
the guest has space for at least two big packets and we don't have at least a
quarter ring to unmap, delay it for at most 1 milisec.
v4:
- use bool
Xen network protocol had implicit dependency on MAX_SKB_FRAGS. Netback has to
handle guests sending up to XEN_NETBK_LEGACY_SLOTS_MAX slots. To achieve that:
- create a new skb
- map the leftover slots to its frags (no linear buffer here!)
- chain it to the previous through skb_shinfo(skb)->frag_lis
This patch changes the grant copy on the TX patch to grant mapping
v2:
- delete branch for handling fragmented packets fit PKT_PROT_LEN sized first
request
- mark the effect of using ballooned pages in a comment
- place setting of skb_shinfo(skb)->tx_flags |= SKBTX_DEV_ZEROCOPY right
before ne
These counters help determine how often the guest sends a packet with more
than MAX_SKB_FRAGS frags.
Signed-off-by: Zoltan Kiss
---
drivers/net/xen-netback/common.h|1 +
drivers/net/xen-netback/interface.c |7 +++
drivers/net/xen-netback/netback.c |1 +
3 files changed, 9 i
RX path need to know if the SKB fragments are stored on pages from another
domain.
v4:
- indentation fixes
Signed-off-by: Zoltan Kiss
---
drivers/net/xen-netback/netback.c | 46 +
1 file changed, 41 insertions(+), 5 deletions(-)
diff --git a/drivers/net/xe
These became obsolete with grant mapping. I've left intentionally the
indentations in this way, to improve readability of previous patches.
v2:
- move the indentation fixup patch here
v4:
- indentation fixes
Signed-off-by: Zoltan Kiss
---
drivers/net/xen-netback/common.h | 37 +-
When FB_EVENT_FB_UNBIND is sent, fbcon has two paths, one path taken
when there is another frame buffer to switch any affected vcs to and
another path when there isn't.
In the case where there is another frame buffer to use,
fbcon_fb_unbind calls set_con2fb_map to remap all of the affected vcs
to
On Mon, Jan 20, 2014 at 01:16:01PM -0800, Greg KH wrote:
> On Mon, Jan 20, 2014 at 10:05:30AM +, Russell King - ARM Linux wrote:
> > On Mon, Jan 20, 2014 at 02:32:34PM +0530, Tushar Behera wrote:
> > > uart_register_driver call binds the driver to a specific device
> > > node through tty_regist
> As a side note, at minimum the semantic and compatibility difference
> needs to be _very_ clearly present in the naming. Something like
> mwait_old_() or mwait_core2_(). That way such dependencies and
> assumptions don't get lost in code restructuring, etc.
Agreed.
We started with mwait_idle() -
On Mon, Jan 20, 2014 at 11:02 AM, David Vrabel wrote:
> On 20/01/14 18:33, Luis R. Rodriguez wrote:
>> Is the delta of what is queued for the next release typically small?
>> Otherwise someone doing development based on linux.git alone should
>> have conflicts with anything on the queue, no?
>
> W
On Mon, 20 Jan 2014, Oleg Nesterov wrote:
> > > At first glance, can't __ATTR_IGNORE_LOCKDEP() use no_validate too ?
> > > (ignoring the fact checkpatch.pl won't be happy). This can simplify
> > > the code, it seems.
> >
> > Well, the macro itself doesn't specify the lockdep class. That happens
>
> I had earlier submitted a patch [1] to remove the hard coded
> major/minor number for Samsung UART driver, but that was rejected
> because of userspace breakage. Without this patch, Samsung UART driver
> can't bind to the hard-coded device node. Changing the default
> major/minor will also not he
Hi Benjamin,
On Fri, Jan 17, 2014 at 02:12:51PM -0500, Benjamin Tissoires wrote:
> Evemu [1] uses uinput to replay devices traces it has recorded. However,
> the way evemu uses uinput is slightly different from how uinput is
> supposed to be used.
> Evemu relies on libevdev, which creates the devi
On Mon, Jan 20, 2014 at 04:39:45PM -0500, Len Brown wrote:
> > As a side note, at minimum the semantic and compatibility difference
> > needs to be _very_ clearly present in the naming. Something like
> > mwait_old_() or mwait_core2_(). That way such dependencies and
> > assumptions don't get lost
On Thu, 2014-01-16 at 13:49 -0500, Jason Cooper wrote:
> > @Ian: Thanks for hunting this down, please keep bothering us with
> > bug reports :)
>
> Yes, please!
No worries there -- it seem Debian has quite a few people who use
kirkwood based systems and will report bugs when they find them...
Th
As described in 2/2 many Intel root ports lack PCIe ACS capabilities
which results in excessively large IOMMU groups. Many of these root
ports do provide isolation capabilities, we just need to use device
specific mechanisms to enable and verify. Long term, I hope we can
round out this list (part
Some devices support PCI ACS-like features, but don't report it using
the standard PCIe capabilities. We already provide hooks for device
specific testing of ACS, but not for device specific enabling of ACS.
This provides that setup hook.
Signed-off-by: Alex Williamson
---
drivers/pci/pci.c
Many of the currently available Intel PCH-based root ports do not
provide PCIe ACS capabilities. Without this, we must assume that
peer-to-peer traffic between multifunction root ports and between
devices behind root ports is possible. This lack of isolation is
exposed by grouping the devices tog
On Mon, Jan 20, 2014 at 09:24:28PM +, Zoltan Kiss wrote:
> A malicious or buggy guest can leave its queue filled indefinitely, in which
> case qdisc start to queue packets for that VIF. If those packets came from an
> another guest, it can block its slots and prevent shutdown. To avoid that, we
> -Original Message-
> From: David Miller [mailto:da...@davemloft.net]
> Sent: Tuesday, January 14, 2014 5:32 PM
> To: Haiyang Zhang
> Cc: net...@vger.kernel.org; KY Srinivasan; o...@aepfle.de;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; driverdev-
> de...@linuxdriverproject.org
> -Original Message-
> From: Haiyang Zhang
> Sent: Monday, January 20, 2014 2:06 PM
> To: David Miller
> Cc: net...@vger.kernel.org; KY Srinivasan; o...@aepfle.de;
> jasow...@redhat.com; linux-kernel@vger.kernel.org; driverdev-
> de...@linuxdriverproject.org
> Subject: RE: [PATCH net-next
On Mon, Jan 20, 2014 at 10:03:48PM +, Wei Liu wrote:
[...]
>
> You beat me to this. Was about to reply to your other email. :-)
>
> It's also worth mentioning that DIV_ROUND_UP part is merely estimation,
> as you cannot possible know the maximum / miminum queue length of all
> other vifs (as
Olaf,
I am cleaning up the code based on your feedback. By the time I am done with my
cleanup, I doubt if
this patch would apply. Do you mind if I were to include your changes here as
part of my cleanup?
Thank you,
K. Y
> -Original Message-
> From: Olaf Hering [mailto:o...@aepfle.de]
On Mon, Jan 20, 2014 at 01:53:13PM -0800, Dmitry Torokhov wrote:
> Hi Benjamin,
>
> On Fri, Jan 17, 2014 at 02:12:51PM -0500, Benjamin Tissoires wrote:
> > Evemu [1] uses uinput to replay devices traces it has recorded. However,
> > the way evemu uses uinput is slightly different from how uinput i
On Mon, Jan 20, KY Srinivasan wrote:
> I am cleaning up the code based on your feedback. By the time I am
> done with my cleanup, I doubt if this patch would apply. Do you mind
> if I were to include your changes here as part of my cleanup?
Yes, thats fine.
Olaf
--
To unsubscribe from this list
On Mon, Jan 20, 2014 at 4:53 PM, Dmitry Torokhov
wrote:
> Hi Benjamin,
>
> On Fri, Jan 17, 2014 at 02:12:51PM -0500, Benjamin Tissoires wrote:
>> Evemu [1] uses uinput to replay devices traces it has recorded. However,
>> the way evemu uses uinput is slightly different from how uinput is
>> suppos
On Mon, Jan 20, 2014 at 05:58:55AM -0800, Christoph Hellwig wrote:
> On Thu, Jan 16, 2014 at 09:07:21AM +1100, Dave Chinner wrote:
> > Yes, I think it can be done relatively simply. We'd have to change
> > the code in xfs_file_aio_write_checks() to check whether EOF zeroing
> > was required rather
> -Original Message-
> From: Olaf Hering [mailto:o...@aepfle.de]
> Sent: Monday, January 20, 2014 2:16 PM
> To: KY Srinivasan
> Cc: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; a...@canonical.com; jasow...@redhat.com
> Subject: Re: [PATCH V2 1/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
Am 18.01.2014 23:46, schrieb Daniel Exner:
> Hi again,
>
> Am 18.01.2014 20:50, schrieb Borislav Petkov:
>> + netdev.
> Thx
>
> Am 18.01.2014 20:49, schrieb Holger Hoffstätte:> [This mail was
> also posted to gmane.linux.kernel.]
>
>> On Sat,
On Mon, Jan 20, 2014 at 11:27:25PM +0100, Daniel Exner wrote:
> I just did the same procedure with Kernel Version 3.13: same poor rates.
>
> I think I will try to see of 3.12.6 was still ok and bisect from there.
Or try something more coarse-grained like 3.11 first, then 3.12 and then
the -rcs in
On Mon, 20 Jan 2014, Alexander Gordeev wrote:
This is an attempt to make handling of admin queue in a
single scope. This update also fixes a IRQ leak in case
nvme_setup_io_queues() failed to allocate enough iomem
and bailed out with -ENOMEM errno.
This definitely seems to improve the code flow,
On Mon, Jan 20, 2014 at 05:17:08PM -0500, Benjamin Tissoires wrote:
> On Mon, Jan 20, 2014 at 4:53 PM, Dmitry Torokhov
> wrote:
> > Hi Benjamin,
> >
> > On Fri, Jan 17, 2014 at 02:12:51PM -0500, Benjamin Tissoires wrote:
> >> Evemu [1] uses uinput to replay devices traces it has recorded. However,
So I pulled this, but one question:
On Mon, Jan 20, 2014 at 8:47 AM, H. Peter Anvin wrote:
> +config RANDOMIZE_BASE
> + bool "Randomize the address of the kernel image"
> + depends on RELOCATABLE
> + depends on !HIBERNATION
How fundamental is that "!HIBERNATION" issue? Right no
401 - 500 of 607 matches
Mail list logo
