On Mon, Sep 01, 2014 at 08:05:34PM +0100, Peter Zijlstra wrote:
> On Mon, Sep 01, 2014 at 07:18:08PM +0100, Mark Rutland wrote:
> > Hi all,
>
> > [ 66.780759] [] rcu_process_callbacks+0x1e3/0x540
>
> > Has anything seen anything like this before? Is this a known issue?
>
> I've not seen it
On Tue, Sep 02, 2014 at 11:24:02AM -0700, Greg Kroah-Hartman wrote:
> On Tue, Sep 02, 2014 at 11:46:35PM +0530, Sudip Mukherjee wrote:
> > From: Sudip Mukherjee
> >
> > removed unused variables
> > fixed sparse warning of context imbalance in 'do_locked_client_insert'
> >
On Tue, Sep 02, 2014 at 02:00:35PM +0100, Daniel Thompson wrote:
> void enable_fiq(int fiq)
> {
> + struct fiq_data *data = lookup_fiq_data(fiq);
> +
> + if (data) {
> + if (data->fiq_chip->fiq_enable)
> + data->fiq_chip->fiq_enable(data->irq_data);
> +
From: Harish Jenny Kandiga Nagaraj
Date: Tue, 2 Sep 2014 14:14:38 +0530
> In one of our random test runs we observed the crash mentioned in the
> previous mail.
>
> After debugging we found out that the call flow of the inline and static
> functions were
> netlink_release
>
On Fri, Aug 22, 2014 at 12:53:04PM -0400, Tejun Heo wrote:
> (the initial posting was missing cc's, reposting)
>
> Due to the use of vmalloc area allocations and page table populations,
> preparing percpu areas require GFP_KERNEL and all the allocator users
> are expected to be able to perform
On Tue 02 Sep 10:28 PDT 2014, Jeffrey Hugo wrote:
> > diff --git a/drivers/hwspinlock/msm_hwspinlock.c
> > b/drivers/hwspinlock/msm_hwspinlock.c
[..]
> > + * Copyright (c) 2013, The Linux Foundation. All rights reserved.
>
> Should the copyright range be updated to include your changes which I
From: Andi Kleen
Use the newly added Broadwell cache event list for Haswell too.
All Haswell and Broadwell events and offcore masks used in these lists
are identical.
However Haswell is very different from the Sandy Bridge
list that was used previously. That fixes a wide range of mis-counting
On Tue, Sep 02, 2014 at 09:17:34PM +0400, Pavel Emelyanov wrote:
> Hi,
>
> There's a problem with getting information about who has a flock on
> a specific file. The thing is that the "owner" field, that is shown in
> /proc/locks is the pid of the task who created the flock, not the one
> who
From: Andi Kleen
Add Broadwell support for Broadwell Client to perf.
This is very similar to Haswell. It uses a new cache event table,
because there were various changes there.
The constraint list has one new event that needs to be handled over Haswell.
The PEBS event list is the same, so we
From: Andi Kleen
Add names for each Haswell model as requested by Peter.
v2: Remove Crystall Well name.
v3: Change names
Signed-off-by: Andi Kleen
---
arch/x86/kernel/cpu/perf_event_intel.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
From: Andi Kleen
71 is a Broadwell, not a Haswell. The model number was added
by mistake earlier.
Remove it for now, until it can be re-added later with
real Broadwell support.
In practice it does not cause a lot of issues because the Broadwell
PMU is very similar to Haswell, but some details
From: Andi Kleen
On Broadwell INST_RETIRED.ALL cannot be used with any period
that doesn't have the lowest 6 bits cleared. And the period
should not be smaller than 128.
Add a new callback to enforce this, and set it for Broadwell.
This is erratum BDM57 and BDM11.
How does this handle the
On Wed, Aug 27 2014 at 14:56 -0600, Thomas Gleixner wrote:
On Wed, 27 Aug 2014, Lina Iyer wrote:
PM QoS and other idle frameworks can do a better job of addressing power
and performance requirements for a cpu, knowing the IRQs that are
affine to that cpu. If a performance request is placed
On Tue, Sep 2, 2014 at 11:18 AM, Hannes Frederic Sowa
wrote:
> Those ASSERT_RTNLs were misplaced and only caught the callers mostly
> from addrconf.c. I don't mind getting reports from stable kernel users
> and fixing those, too (or help fixing those). ASSERT_RTNL is not
> dangerous.
>
> We had a
Hi,
On Mon, Sep 1, 2014 at 9:14 PM, Bjorn Helgaas wrote:
> [+cc Linus (author of ad7edfe04908), Matthew (author of 07ff9220908c
> from full history), Yinghai (author of 2f5d8e4ff947), Richard]
>
> On Thu, Aug 28, 2014 at 3:55 PM, Rajat Jain wrote:
>> The PCIe root port of the Intel Haswell CPU,
On 09/01/2014 07:47 PM, Sebastian Andrzej Siewior wrote:
> Comparing it with serial-omap I see the same thing: I takes approx the
> same amount of data until the first one is displayed. After a lot of
> "long" writes which wake the chip up from idle I manage to freeze both,
> the serial-omap
On Tue, Sep 2, 2014 at 11:21 AM, Eric Dumazet wrote:
> On Tue, 2014-09-02 at 11:15 -0700, Cong Wang wrote:
>
>> That is what we do when backporting patches, I can do that if David asks
>> me to backport it, but you know for netdev that is David's work.
>>
>> (I am not saying I don't want to help
Changes since 20140901:
The akpm-current tree lost its conflict against Linus' tree and two
patches from it got applied.
Non-merge commits (relative to Linus' tree): 3078
2790 files changed, 105584 insertions(+), 81173 deletions(-)
I have created today's linux-next tree at
On Tue, Sep 02, 2014 at 11:46:35PM +0530, Sudip Mukherjee wrote:
> From: Sudip Mukherjee
>
> removed unused variables
> fixed sparse warning of context imbalance in 'do_locked_client_insert'
> different lock contexts for basic block
>
> Signed-off-by: Sudip Mukherjee
>
On Mon, Sep 1, 2014 at 10:14 PM, Frederic Weisbecker wrote:
> I'll send "nohz: Restore NMI safe local irq work for local nohz kick"
> as a fix for 3.17 and the rest will have to wait for 3.18 as it's a
> complicated
> fix for a long standing bug.
I've been running with the full series since you
On Tue, 2014-09-02 at 11:15 -0700, Cong Wang wrote:
> That is what we do when backporting patches, I can do that if David asks
> me to backport it, but you know for netdev that is David's work.
>
> (I am not saying I don't want to help him, I just want to point out the fact.
> I am very pleased
On Tue, Sep 2, 2014, at 20:04, Cong Wang wrote:
> On Tue, Sep 2, 2014 at 10:58 AM, Hannes Frederic Sowa
> wrote:
> > Hi Cong,
> >
> > On Tue, Sep 2, 2014, at 18:50, Cong Wang wrote:
> >> On Fri, Aug 29, 2014 at 6:51 PM, Hannes Frederic Sowa
> >> wrote:
> >> >
> >> > Also rtnl_lock and
From: Sudip Mukherjee
removed unused variables
fixed sparse warning of context imbalance in 'do_locked_client_insert'
different lock contexts for basic block
Signed-off-by: Sudip Mukherjee
---
v1 of the patch of the patch just fixed the sparse warning.
On suggestion
On Tue, Sep 2, 2014 at 11:11 AM, Eric Dumazet wrote:
> On Tue, 2014-09-02 at 11:04 -0700, Cong Wang wrote:
>> On Tue, Sep 2, 2014 at 10:58 AM, Hannes Frederic Sowa
>
>> > I definitely don't have a problem cleaning this up in net-next. I wanted
>> > a minimal patch for stable because I didn't
On Tue, 2014-09-02 at 11:04 -0700, Cong Wang wrote:
> On Tue, Sep 2, 2014 at 10:58 AM, Hannes Frederic Sowa
> > I definitely don't have a problem cleaning this up in net-next. I wanted
> > a minimal patch for stable because I didn't check history where and when
> > additional users of
James Morris wrote:
> Which of these need to go into current Linus?
>
> #4 looks like it should.
All of them, preferably, though I'm okay with #3 being deferred.
David
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
2014-09-02 19:07 GMT+02:00 Paul E. McKenney :
> On Fri, Aug 29, 2014 at 03:08:20PM +0200, Stefan Hengelein wrote:
>> Every choice item of the "Build-forced no-CBs CPUs" choice had a
>> dependency to RCU_NOCB_CPU. It's more comprehensible if the choice
>> itself has the dependency instead of every
On the Toshiba Tecra Z40, after a suspend-to-disk, some FN hotkeys
driven by toshiba_acpi are not functional.
Calling the ACPI object ENAB on resume makes them back alive.
Signed-off-by: Benjamin Tissoires
---
Hi guys,
we noticed this problem on a Toshiba Z40. I kind of brute-forced the
On Tue, Sep 2, 2014 at 10:58 AM, Hannes Frederic Sowa
wrote:
> Hi Cong,
>
> On Tue, Sep 2, 2014, at 18:50, Cong Wang wrote:
>> On Fri, Aug 29, 2014 at 6:51 PM, Hannes Frederic Sowa
>> wrote:
>> >
>> > Also rtnl_lock and rcu_read_lock compose in that order, so we don't need
>> > to change
On Aug 31, 2014, at 5:52 PM, Rusty Russell wrote:
> Jeff Kirsher writes:
>> From: Mark Rustad
>>
>> Resolve a missing-field-initializer warning, that is produced
>> by every reference to module_param_call, by using designated
>> initialization for the first field. That is enough to silence
>>
save_xstate_sig()->drop_init_fpu() doesn't look right. setup_rt_frame()
can fail after that, in this case the next setup_rt_frame() triggered
by SIGSEGV won't save fpu simply because the old state was lost. This
obviously mean that fpu won't be restored after sys_rt_sigreturn() from
SIGSEGV
__thread_fpu_begin() checks X86_FEATURE_EAGER_FPU by hand, we have
a helper for that.
Signed-off-by: Oleg Nesterov
Reviewed-by: Suresh Siddha
---
arch/x86/include/asm/fpu-internal.h |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/x86/include/asm/fpu-internal.h
Both 32bit and 64bit versions of copy_thread() do memset(ptrace_bps)
twice for no reason, kill the 2nd memset().
Signed-off-by: Oleg Nesterov
---
arch/x86/kernel/process_32.c |4 +---
arch/x86/kernel/process_64.c |2 --
2 files changed, 1 insertions(+), 5 deletions(-)
diff --git
Cosmetic, but imho memset(>thread.fpu, 0) is not good simply
because it hides the (important) usage of ->has_fpu/etc from grep.
Change this code to initialize the members explicitly.
And note that ->last_cpu = 0 looks simply wrong, this can confuse
fpu_lazy_restore() if per_cpu(fpu_owner_task, 0)
Add preempt_disable() + preempt_enable() around math_state_restore() in
__restore_xstate_sig(). Otherwise __switch_to() after __thread_fpu_begin()
can overwrite fpu->state we are going to restore.
Signed-off-by: Oleg Nesterov
Cc: sta...@vger.kernel.org
Reviewed-by: Suresh Siddha
---
Cosmetic, but I think thread.fpu_counter should be initialized in
arch_dup_task_struct() too, along with other "fpu" variables. And
probably it make sense to turn it into thread.fpu->counter.
Signed-off-by: Oleg Nesterov
Reviewed-by: Suresh Siddha
---
arch/x86/kernel/process.c|1 +
arch_dup_task_struct() copies thread.fpu if fpu_allocated(), this
looks suboptimal and misleading. Say, a forking process could use
FPU only once in a signal handler but now tsk_used_math(src) == F,
in this case the child gets a copy of fpu->state for no reason. The
child won't use the saved
Peter, please consider this series for inclusion.
I added v2 tag to avoid the confusion but the patches are the same,
except the new/offtopic but hopefully trivial 7/7.
2-6 were acked by Suresh (thanks!), the 1st patch still has no acks
although iiuc Linus seems to agree with this change.
Oleg.
Hi Linus,
This fixes an ARM allmodconfig build problem.
Bjorn
The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:
Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git
On Tue, Sep 02, 2014 at 11:40:16AM +0200, Peter Zijlstra wrote:
> On Mon, Sep 01, 2014 at 09:04:38PM +0200, Peter Zijlstra wrote:
> > On Mon, Sep 01, 2014 at 09:46:42AM -0700, Guenter Roeck wrote:
> > > Yes, the problem is still seen in next-140829. See qemu test results at
> > >
Hi Cong,
On Tue, Sep 2, 2014, at 18:50, Cong Wang wrote:
> On Fri, Aug 29, 2014 at 6:51 PM, Hannes Frederic Sowa
> wrote:
> >
> > Also rtnl_lock and rcu_read_lock compose in that order, so we don't need
> > to change dev_get_by_flags, but as this is the only user it sure is
> > possible. RCU
On Tue, 02 Sep 2014 01:48:40 +0200
"Rafael J. Wysocki" wrote:
> On Thursday, August 28, 2014 09:56:08 PM Jacob Pan wrote:
> > Many CPUs do not support complete set of RAPL domains, as a
> > result this detection failed message is very misleading and
> > annoying. So loweab Pan
>
> What about
Naveen,
On Tue, Sep 02, 2014 at 08:54:52PM +0530, Naveen Krishna Chatradhi wrote:
> The following compilation error occurs on 64-bit Exynos7 SoC:
>
> drivers/irqchip/exynos-combiner.c: In function ‘combiner_irq_domain_map’:
> drivers/irqchip/exynos-combiner.c:162:2: error: implicit declaration
Many CPUs do not support complete set of RAPL domains, as a
result this detection failed message is very misleading and
can be annoying.
[5.082632] intel_rapl: RAPL domain core detection failed
[5.088370] intel_rapl: RAPL domain uncore detection failed
So lower the warning message to
On Tue, Sep 02, 2014 at 06:40:21PM +0100, Sudeep Holla wrote:
> Hi Greg,
>
> On 02/09/14 18:26, Greg Kroah-Hartman wrote:
> >On Tue, Sep 02, 2014 at 06:22:07PM +0100, Sudeep Holla wrote:
> >>Hi Greg,
> >>
> >>On 22/08/14 12:29, Sudeep Holla wrote:
> >>>From: Sudeep Holla
> >>>
> >>>This patch
On Mon, Sep 01, 2014 at 08:47:12AM -0400, Dipak Zope wrote:
> Signed-off-by: Dipak Zope
> ---
> drivers/staging/android/uapi/binder.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/staging/android/uapi/binder.h
> b/drivers/staging/android/uapi/binder.h
> index
On 09/02/2014 07:46 PM, Paolo Bonzini wrote:
*/
if (unlikely(real_gfn == UNMAPPED_GVA))
goto error;
@@ -1974,10 +1974,28 @@ static void nested_svm_inject_npf_exit(struct kvm_vcpu
*vcpu,
{
struct vcpu_svm *svm = to_svm(vcpu);
-
Indeed, my crash dump occurred on kernel 2.6.30 (RH 6.5 distribution) and in
this version function remove_hrtimer doesn't preserve "HRTIMER_STATE_CALLBACK"
flag and triggers hard lockup.
So this bug was already fixed in version 2.6.35 to set the flag by
remove_hrtimer function.
Seems that
Hi,
On Mon, Sep 01, 2014 at 01:25:31PM +0200, Ricardo Ribalda Delgado wrote:
> Hello Felipe
>
> I think that you have forgotten about this patch :). It is needed by
> usb3380 in usb3.0 mode. Otherwise the device keeps reseting.
it's in my testing/fixes. I'm pretty much done with testing, just
On Monday, September 01, 2014 4:04 AM, Ian Abbott wrote:
> Continue to clean up the amplc_pci230 driver code and remove the legacy
> attach mechanism, since it isn't very useful for this driver (see PATCH
> 05/28).
Reviewed-by: H Hartley Sweeten
--
To unsubscribe from this list: send the line
On Tuesday 02 September 2014 19:42:52 Alexander Shiyan wrote:
> > > -struct regmap *syscon_regmap_lookup_by_pdevname(const char *s)
> > > -{
> > > - struct device *dev;
> > > - struct syscon *syscon;
> > > -
> > > - dev = driver_find_device(_driver.driver, NULL, (void *)s,
> > > -
On Tue, Sep 02, 2014 at 06:47:14PM +0200, Oleg Nesterov wrote:
> But since I already wrote v2 yesterday, let me show it anyway. Perhaps
> you will notice something wrong immediately...
>
> So, once again, this patch adds the ugly "goto" into schedule(). OTOH,
> it removes the ugly
On Mon, Sep 01, 2014 at 10:24:40AM +0100, Ian Abbott wrote:
> On 2014-09-01 10:23, Ian Abbott wrote:
> >On 2014-08-31 20:45, Chase Southwood wrote:
> >>Sparse shows a couple of warnings like:
> >>
> >>drivers/staging/comedi/drivers/usbduxsigma.c:787:23: warning: cast to
> >>restricted __be32
> >>
Hi Greg,
On 02/09/14 18:26, Greg Kroah-Hartman wrote:
On Tue, Sep 02, 2014 at 06:22:07PM +0100, Sudeep Holla wrote:
Hi Greg,
On 22/08/14 12:29, Sudeep Holla wrote:
From: Sudeep Holla
This patch adds a new function to create per-cpu devices.
This helps in:
1. reusing the device
On Tue, Sep 2, 2014 at 8:48 AM, Arnd Bergmann wrote:
> On Tuesday 02 September 2014 08:20:53 Rob Herring wrote:
>> >>
>> >> This alone is not okay. There is no such implementation of hardware.
>> >
>> > But the SBSA explicitly allows this. I don't know of any vendor who just
>> > implements the
Rationale behind this change:
- F2x1xx addresses were stopped from being mapped explicitly to DCT1
from F15h (OR) onwards. They use _dct[0:1] mechanism to access the
registers. So we should move away from using address ranges to select
DCT for these families.
- On newer processors, the
On Mon, Sep 01, 2014 at 11:52:35PM +0800, sunwxg wrote:
> From: Sun Wang
>
> Fix the style error checking by checkpatch.pl
> ERROR: space required after that ','
>
> Signed-off-by: Sun Wang
>
> ---
> drivers/staging/lustre/lustre/lov/lov_pack.c | 2 +-
> 1 file changed, 1 insertion(+), 1
On 8/29/2014 5:14 PM, Bjorn Andersson wrote:
From: Kumar Gala
Add driver for Qualcomm MSM Hardware Mutex block that exists on
newer Qualcomm SoCs.
Cc: Jeffrey Hugo
Cc: Eric Holmberg
Cc: Courtney Cavin
Signed-off-by: Kumar Gala
[bjorn: added pm_runtime calls, from Courtney,
added
On 08/29/2014 03:14 PM, Andrew Bresticker wrote:
The Global Interrupt Controller (GIC) present on certain MIPS systems
can be used to route external interrupts to individual VPEs and CPU
interrupt vectors. It also supports a timer and software-generated
interrupts.
Signed-off-by: Andrew
On Tue, Sep 02, 2014 at 06:22:07PM +0100, Sudeep Holla wrote:
> Hi Greg,
>
> On 22/08/14 12:29, Sudeep Holla wrote:
> >From: Sudeep Holla
> >
> >This patch adds a new function to create per-cpu devices.
> >This helps in:
> >1. reusing the device infrastructure to create any cpu related
> >
Hi Greg,
On 22/08/14 12:29, Sudeep Holla wrote:
From: Sudeep Holla
This patch adds a new function to create per-cpu devices.
This helps in:
1. reusing the device infrastructure to create any cpu related
attributes and corresponding sysfs instead of creating and
dealing with raw
On Sat, Aug 30, 2014 at 11:23:56PM +, Scot Doyle wrote:
> On Sat, 30 Aug 2014, Jason Gunthorpe wrote:
>
> > On Fri, Aug 29, 2014 at 11:59:32PM +, Scot Doyle wrote:
> >
> >> I tried calling tpm_get_timeouts only during the interrupt test, but again
> >> was timed out after 30 seconds. The
On Tue, Sep 2, 2014 at 9:50 AM, Paolo Bonzini wrote:
> Il 02/09/2014 18:47, David Matlack ha scritto:
>>> > Ping?
>> Sorry for the delay. I think the patches look good. And patch 3/3 still
>> fixes the bug I was originally seeing, so I'm happy :). I just had one
>> small comment (see my reply to
On Tue, Sep 2, 2014 at 9:49 AM, Paolo Bonzini wrote:
> Il 02/09/2014 18:44, David Matlack ha scritto:
>> >
>> > -#define MMIO_GEN_SHIFT 19
>> > -#define MMIO_GEN_LOW_SHIFT 9
>> > -#define MMIO_GEN_LOW_MASK ((1 << MMIO_GEN_LOW_SHIFT) - 1)
>> > +#define
Hi,
There's a problem with getting information about who has a flock on
a specific file. The thing is that the "owner" field, that is shown in
/proc/locks is the pid of the task who created the flock, not the one
who _may_ hold it.
If the flock creator shared the file with some other task (by
On Tue, Sep 02, 2014 at 11:55:58AM -0500, Christoph Lameter wrote:
> On Tue, 2 Sep 2014, Paul E. McKenney wrote:
>
> > Added by ac1bea85781e (sched,rcu: Make cond_resched() report RCU quiescent
> > states), removed by 4a81e8328d379 (rcu: Reduce overhead of cond_resched()
> > checks for RCU). So,
On Tue, Sep 2, 2014 at 1:02 PM, Bryan Wu wrote:
> On Tue, Sep 2, 2014 at 2:03 AM, Jiri Kosina wrote:
>> This reverts commit 8b37e1bef5a6b60e949e28a4db3006e4b00bd758.
>>
>> It's broken as it changes led_blink_set() in a way that it can now sleep
>> (while synchronously waiting for workqueue to be
Hi Linus,
Hugh, Jiri and many other people found a kernel oops due to a LED
change merged recently. Now the right fix might just revert it and
unblock the kernel oops. Please check the bug report in the patch
commit message and consider merge the following changes since commit
Hello,
2014-08-24, 23:56:03 +0900, Akinobu Mita wrote:
> Replace memblock_find_in_range() and memblock_reserve() with
> memblock_alloc_range().
>
> Signed-off-by: Akinobu Mita
> Cc: linux...@kvack.org
This patch is included in linux-next, and when I boot next-20140901,
on a 32-bit build, I get
This patch adds the ST glue logic to manage the DWC3 HC
on STiH407 SoC family. It manages the powerdown signal,
and configures the internal glue logic and syscfg registers.
Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
drivers/usb/dwc3/Kconfig | 9
This patch documents the device tree documentation required for
the ST usb3 controller glue layer found in STiH407 devices.
Signed-off-by: Giuseppe Cavallaro
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
Documentation/devicetree/bindings/usb/dwc3-st.txt | 68 +++
1
This patch adds the new dwc3-st.c glue driver found on
STMicroelectronics stih407 consumer electronics SoC's into the STI
arch section of the maintainers file.
Signed-off-by: Peter Griffin
Acked-by: Lee Jones
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS
This series adds support for the ST glue logic which wraps the DWC3 controller
on STiH407 SoC family chipsets.
Changes since v4
- Fix bug with setting bits in usb control register
- Remove superflous '\n'
- Change default Kconfig to make default same as other platforms
- Update dt doc example
On Fri, Aug 29, 2014 at 03:08:20PM +0200, Stefan Hengelein wrote:
> Every choice item of the "Build-forced no-CBs CPUs" choice had a
> dependency to RCU_NOCB_CPU. It's more comprehensible if the choice
> itself has the dependency instead of every choice item.
> The choice itself doesn't need to be
On Tue 02 Sep 05:36 PDT 2014, Linus Walleij wrote:
> A bit dirty to have this in this driver, but who cares.
>
Indeed, but we figured the taint was small enough to justify not creating
cross-references to a separate driver.
> Does the APQ8064 accompanying PMIC also have the ability to
>
On Tue, Sep 2, 2014 at 2:03 AM, Jiri Kosina wrote:
> This reverts commit 8b37e1bef5a6b60e949e28a4db3006e4b00bd758.
>
> It's broken as it changes led_blink_set() in a way that it can now sleep
> (while synchronously waiting for workqueue to be cancelled). That's a
> problem, because it's possible
Il 02/09/2014 18:46, Paolo Bonzini ha scritto:
>> > How about an io-port emulated on
>> > L1 but passed through to L2 by the nested hypervisor. On emulation of
>> > INS or OUTS, KVM would need to read/write to an L2 address space,
> It would need to read/write to *L1* (that's where the VMCB's IOIO
On Tue, Sep 02, 2014 at 06:46:06PM +0200, Paolo Bonzini wrote:
> Il 02/09/2014 18:33, Joerg Roedel ha scritto:
> > Comment is true, but doesn't make the check below obsolete, no?
>
> No, it doesn't. I'll rewrite it as
>
> /*
>* This cannot happen unless the guest is playing
Jens Axboe writes:
> On 09/02/2014 09:02 AM, Ming Lei wrote:
>> QUEUE_FLAG_NO_SG_MERGE is set at default for blk-mq devices,
>> so bio->bi_phys_segment computed may be bigger than
>> queue_max_segments(q) for blk-mq devices, then drivers will
>> fail to handle the case, for example, BUG_ON() in
On Tue 02 Sep 06:13 PDT 2014, Georgi Djakov wrote:
> Currently the value used for specify that interrupts from the gpio should
> be routed to the application processor is hardcoded for all Qualcomm SoCs.
> But the new APQ8084 SoC uses a different value. To resolve this, we make
> this value
On Tue, Sep 02, 2014 at 06:23:27PM +0300, Dan Carpenter wrote:
> On Tue, Sep 02, 2014 at 08:44:27PM +0530, Sudip Mukherjee wrote:
> > On Tue, Sep 02, 2014 at 05:05:32PM +0300, Dan Carpenter wrote:
> > > On Tue, Sep 02, 2014 at 04:39:47PM +0530, Sudip Mukherjee wrote:
> > > > fixed sparse warning :
Il 02/09/2014 18:02, Valentine Sinitsyn ha scritto:
>>
> I can confirm the initial bug I observed is fixed with these patches
> (applied to 3.16.1).
>
> All tests in kvm-unit-test's master also pass, except for ioio which is
> (probably) affected by another (unrelated) bug fixed by Jan back in
On Tue, 2 Sep 2014, Paul E. McKenney wrote:
> Added by ac1bea85781e (sched,rcu: Make cond_resched() report RCU quiescent
> states), removed by 4a81e8328d379 (rcu: Reduce overhead of cond_resched()
> checks for RCU). So, as you say, no effect on contemporary kernels.
Well not sure what to make
* Sebastian Reichel [140901 20:06]:
> Hi,
>
> On Mon, Sep 01, 2014 at 07:47:53PM +0200, Sebastian Andrzej Siewior wrote:
> > On 08/29/2014 06:12 PM, Tony Lindgren wrote:
> > > Looks like the paste bug is there for sure, doing off idle and pasting
> > > 240 characters to the console can hang the
Mark,
On Tue, Sep 2, 2014 at 9:31 AM, Mark Brown wrote:
> On Tue, Sep 02, 2014 at 09:14:29AM -0700, Doug Anderson wrote:
>> The original bindings for rk808 didn't include input supplies. Add
>> them.
>
> Acked-by: Mark Brown
>
> You probably want to send this to Lee...
Good point. I think it
On Tue, Sep 2, 2014 at 8:55 AM, Josh Boyer wrote:
> On Tue, Sep 2, 2014 at 5:03 AM, Jiri Kosina wrote:
>> This reverts commit 8b37e1bef5a6b60e949e28a4db3006e4b00bd758.
>>
>> It's broken as it changes led_blink_set() in a way that it can now sleep
>> (while synchronously waiting for workqueue to
On Fri, Aug 29, 2014 at 6:51 PM, Hannes Frederic Sowa
wrote:
>
> Also rtnl_lock and rcu_read_lock compose in that order, so we don't need
> to change dev_get_by_flags, but as this is the only user it sure is
> possible. RCU locked version is just easier composeable, so I wouldn't
> touch that if
Il 02/09/2014 18:47, David Matlack ha scritto:
>> > Ping?
> Sorry for the delay. I think the patches look good. And patch 3/3 still
> fixes the bug I was originally seeing, so I'm happy :). I just had one
> small comment (see my reply to patch 2/3).
>
I answered that question now. Can I add
On 09/02, Oleg Nesterov wrote:
>
> OK. So this patch should probably work. But let me think again and send
> it tommorrow. Because today (and yesterday) I didn't really sleep ;)
But since I already wrote v2 yesterday, let me show it anyway. Perhaps
you will notice something wrong immediately...
Il 02/09/2014 18:44, David Matlack ha scritto:
> >
> > -#define MMIO_GEN_SHIFT 19
> > -#define MMIO_GEN_LOW_SHIFT 9
> > -#define MMIO_GEN_LOW_MASK ((1 << MMIO_GEN_LOW_SHIFT) - 1)
> > +#define MMIO_GEN_SHIFT 20
> > +#define MMIO_GEN_LOW_SHIFT
On Tue, Sep 2, 2014 at 8:42 AM, Paolo Bonzini wrote:
> Il 29/08/2014 12:31, Paolo Bonzini ha scritto:
>> David and Xiao, here's my take on the MMIO generation patches. Now
>> with documentation, too. :) Please review!
>>
>> David Matlack (2):
>> kvm: fix potentially corrupt mmio cache
>>
Il 02/09/2014 18:33, Joerg Roedel ha scritto:
> Ah, here you add emulation of these bits.
>
> On Tue, Sep 02, 2014 at 05:13:48PM +0200, Paolo Bonzini wrote:
>> This is similar to what the EPT code does with the exit qualification.
>> This allows the guest to see a valid value for bits 33:32.
>>
Le 02/09/2014 12:41, Pablo Neira Ayuso a écrit :
On Tue, Sep 02, 2014 at 12:14:27PM +0200, leroy christophe wrote:
Calling 'iptables-compat -L', first time nothing is listed on the screen.
Second try, it generates following Oops.
I'm going to pass this patch to -stable asap:
commit
On Fri, Aug 29, 2014 at 3:31 AM, Paolo Bonzini wrote:
> From: David Matlack
>
> vcpu exits and memslot mutations can run concurrently as long as the
> vcpu does not aquire the slots mutex. Thus it is theoretically possible
> for memslots to change underneath a vcpu that is handling an exit.
>
>
On Tue, 2014-09-02 at 01:37 +0200, Rafael J. Wysocki wrote:
> From: Rafael J. Wysocki
>
> After commit d431cbc53cb7 (PM / sleep: Simplify sleep states sysfs
> interface code) the pm_states[] array is not populated initially,
> which causes setup_test_suspend() to always fail and the suspend
>
On Tue 02 Sep 06:13 PDT 2014, Georgi Djakov wrote:
> Define a new binding for the Qualcomm TLMM (Top-Level Mode Mux) based pin
> controller inside the APQ8084.
>
> Acked-by: Bjorn Andersson
Don't remember giving you this...
But, with the s/sdc3/sdc2 below I think it looks good; so with that
On Tue, Sep 2, 2014 at 1:29 AM, Sabrina Dubroca wrote:
>
> v2:
> - based on net
> - keep dev_get_by_flags_rcu and RCU in ipv6_sock_ac_*
> - remove two ASSERT_RTNL() that are not necessary
There is no point to keep RCU here. Hannes' reply doesn't make
any sense.
--
To unsubscribe from this
On Tue, Sep 02, 2014 at 12:49:16PM +0100, Daniel Thompson wrote:
> On 28/08/14 16:01, Russell King - ARM Linux wrote:
> > I just asked Paul McKenney, our RCU expert... essentially, yes, RCU
> > stuff itself is safe in this context. However, RCU stuff can call into
> > lockdep if lockdep is
On 09/03/2014 12:37 AM, OGAWA Hirofumi wrote:
> Seunghun Lee writes:
>
>> diff --git a/fs/fat/inode.c b/fs/fat/inode.c
>> index 756aead..6992dea 100644
>> --- a/fs/fat/inode.c
>> +++ b/fs/fat/inode.c
>> @@ -1307,12 +1307,9 @@ static unsigned long calc_fat_clusters(struct
>> super_block *sb)
>>
This patch fixes the following checkpatch.pl warning in lnet/lnet/lib-eq.c:
WARNING: space prohibited between function name and open parenthesis '('
Signed-off-by: Mathieu OTHACEHE
---
This patch is part of task 10 of the eudyptula challenge
drivers/staging/lustre/lnet/lnet/lib-eq.c | 12
301 - 400 of 1554 matches
Mail list logo