Fixes tip commit b3fd4f03ca0b (locking/rwsem: Avoid deceiving lock spinners).
Ming reported soft lockups occurring when running xfstest due to
commit b3fd4f03ca0b.
When doing optimistic spinning in rwsem, threads should stop spinning when
the lock owner is not running. While a thread is spinning
> Von: Kim Phillips [kim.phill...@freescale.com]
> Gesendet: Samstag, 7. März 2015 01:46
> An: Herbert Xu; Benjamin Herrenschmidt; Paul Mackerras; Michael Ellerman
> Cc: Markus Stockhausen; linux-cry...@vger.kernel.org;
> linuxppc-...@lists.ozlabs.org; linux-kernel@vger.kernel.org
> Betreff:
Here all details (dmesg, lspci etc):
https://bugzilla.kernel.org/show_bug.cgi?id=94261
The machine is:
LENOVO 90BX0018IX/Aptio CRB, BIOS O07KT49AUS 12/18/2014
OS is a Debian Wheezy amd64.
The issue is that USB ports work only starting the kernel with
"pci=noacpi" parameter.
Without it, nothing
On Sat, 2015-03-07 at 13:54 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 12:31 PM, Jason Low wrote:
> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> > Cc: Ming Lei
> > Cc: Davidlohr Bueso
> > Signed-off-by: Jason Low
>
> Reported-and-tested-by: Ming Lei
Thanks!
> > static
On Fri, 2015-03-06 at 20:44 -0800, Davidlohr Bueso wrote:
> On Fri, 2015-03-06 at 20:31 -0800, Jason Low wrote:
> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> >
> > Just in case, here's the updated patch which addresses Linus's comments
> > and with a changelog.
> >
> > Note: The
Add missing "cdns,at91sam9260-macb", "atmel,sama5d3-gem" and
"atmel,sama5d4-gem" compatible strings.
Signed-off-by: Boris Brezillon
Reviewed-by: Alexandre Belloni
Acked-by: Nicolas Ferre
---
Documentation/devicetree/bindings/net/macb.txt | 5 -
1 file changed, 4 insertions(+), 1
Hello Dave,
On Fri, 06 Mar 2015 15:18:30 -0500 (EST)
David Miller wrote:
> From: Boris Brezillon
> Date: Fri, 6 Mar 2015 11:48:39 +0100
>
> > Changes since v2:
> > - rebase after changed brought by [1]
>
> Ugh, actually I'm tossing all of your changes. Please do not make
> complex
Some at91 SoCs embed a 10/100 Mbit Ethernet IP, that is based on the
at91sam9260 SoC.
Fix at91 DTs accordingly.
Signed-off-by: Boris Brezillon
Reviewed-by: Alexandre Belloni
---
arch/arm/boot/dts/at91sam9260.dtsi | 2 +-
arch/arm/boot/dts/at91sam9263.dtsi | 2 +-
Hello,
The rm9200 boards use the dedicated at91_ether driver instead of the
regular macb driver.
Both the macb and at91_ether drivers can be compiled as separated
modules.
Since the at91_ether driver uses code from the macb driver, at91_ether.ko
depends on macb.ko.
However the macb.ko module
With multi platform support those sections could lead to unexpected
behavior if both ARCH_AT91 and another ARM SoC using the MACB IP are
selected.
Add two new capabilities to encode the default MII mode and the presence
of a CLKEN bit in USRIO register.
Then define the appropriate config for IPs
Enable EEE support for MV88E6352.
Signed-off-by: Guenter Roeck
---
Changes since RFT:
- Additional testing; no code changes.
drivers/net/dsa/mv88e6352.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/net/dsa/mv88e6352.c b/drivers/net/dsa/mv88e6352.c
index 1ebd8f9..7bc5998 100644
EEE configuration is similar for the various MV88E6xxx chips.
Add generic support for it.
Signed-off-by: Guenter Roeck
Reviewed-by: Florian Fainelli
---
Changes since RFT:
- Additional testing; no code changes
- Dropped comment about phy_init_eee
drivers/net/dsa/mv88e6xxx.c | 51
From: Cyrille Pitchen
macb and at91_ether drivers can be compiled as modules, but the at91_ether
driver use some functions and variables defined in the macb one, thus
creating a dependency on the macb driver.
Since these drivers are sharing the same logic we can easily merge
at91_ether into
From: Cyrille Pitchen
Most of the functions from the Common Clk Framework handle NULL pointer as
input argument.
Since the TX clock is optional, we now set tx_clk to NULL value
instead of ERR_PTR(-ENOENT) when this clock is not available. This simplifies
the clock management and avoid the need
This patch is a continuation of the rescind handling cleanup work. We cannot
block in the global message handling work context especially if we are blocking
waiting for the host to wake us up. I would like to thank
Dexuan Cui for observing this problem.
Signed-off-by: K. Y. Srinivasan
---
-
On Sat, Mar 7, 2015 at 12:31 PM, Jason Low wrote:
> On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
>
> Just in case, here's the updated patch which addresses Linus's comments
> and with a changelog.
>
> Note: The changelog says that it fixes (locking/rwsem: Avoid deceiving
> lock spinners),
From: Dexuan Cui
Without this patch, hv_fcopy_daemon's hv_copy_data() -> pwrite()
will fail for >2GB file offset.
Signed-off-by: Alex Ng
Signed-off-by: Dexuan Cui
Cc: K. Y. Srinivasan
Signed-off-by: K. Y. Srinivasan
---
tools/hv/Makefile |2 +-
1 files changed, 1 insertions(+), 1
Export the vmbus_sendpacket_pagebuffer_ctl() interface.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c
index da53180..e58cdb7 100644
--- a/drivers/hv/channel.c
+++
From: Vitaly Kuznetsov
When add_memory() fails the following BUG is observed:
[ 743.646107] hv_balloon: hot_add memory failed error is -17
[ 743.679973]
[ 743.680930] =
[ 743.680930] [ BUG: bad unlock balance detected! ]
[ 743.680930]
From: Vitaly Kuznetsov
Memory blocks can be onlined in random order. When this order is not natural
some memory pages are not onlined because of the redundant check in
hv_online_page().
Here is a real world scenario:
1) Host tries to hot-add the following (process_hot_add):
From: Nick Meier
HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the usage context,
the value may be truncated. This patch is in response from the following
email from Intel:
[char-misc:char-misc-testing 25/45] drivers/hv/vmbus_drv.c:67:9: sparse:
constant
From: Dan Carpenter
The indenting makes it clear that there were curly braces intended here.
Fixes: 2dd37cb81580 ('Drivers: hv: vmbus: Handle both rescind and offer
messages in the same context')
Signed-off-by: Dan Carpenter
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c |
This patch-set has miscellaneous fixes for both the VMBUS as well as the balloon
driver. There is also a fix for the hv tools makefile.
In this version of the patchset, I have included a patch from Dexuan.
Furthermore, I have addressed a memory leak issue in the patch:
Drivers: hv: vmbus: Perform
we were dereferencing sdkp first and then we were checking for it
being NULL.
Signed-off-by: Sudip Mukherjee
---
drivers/scsi/sd_dif.c | 14 --
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/drivers/scsi/sd_dif.c b/drivers/scsi/sd_dif.c
index 14c7d42..a514645 100644
Hi,
On Fri, Mar 06, 2015 at 11:08:53AM +0100, Robert Baldyga wrote:
> LPM capability is hardware property, so now it's moved to DT.
you need a better commit log here.
> Signed-off-by: Robert Baldyga
> ---
> Documentation/devicetree/bindings/usb/dwc3.txt | 1 +
> drivers/usb/dwc3/Kconfig
modified the code to keep the logic same but removed some indention.
Signed-off-by: Sudip Mukherjee
---
this patch will generate checkpatch warning about line more than 80char,
and too many use of tab. but unless the total function is rewrtten it will
be difficult to fix that.
these variables were assigned some values but they were never being
reused again.
Signed-off-by: Sudip Mukherjee
---
this patch will generate some checkpatch warning about line being above 80char,
but the code is so much indented that it is difficult to break the line.
> -Original Message-
> From: K. Y. Srinivasan [mailto:k...@microsoft.com]
> Sent: Friday, March 6, 2015 9:10 PM
> To: gre...@linuxfoundation.org; linux-kernel@vger.kernel.org;
> de...@linuxdriverproject.org; o...@aepfle.de; a...@canonical.com;
> vkuzn...@redhat.com
> Cc: KY Srinivasan
>
On Fri, 2015-03-06 at 20:31 -0800, Jason Low wrote:
> On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
>
> Just in case, here's the updated patch which addresses Linus's comments
> and with a changelog.
>
> Note: The changelog says that it fixes (locking/rwsem: Avoid deceiving
> lock
On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
Just in case, here's the updated patch which addresses Linus's comments
and with a changelog.
Note: The changelog says that it fixes (locking/rwsem: Avoid deceiving
lock spinners), though I still haven't seen full confirmation that it
addresses
On Fri, 2015-03-06 at 15:50 -0800, Olof Johansson wrote:
> On Fri, Mar 6, 2015 at 2:56 PM, Benjamin Herrenschmidt
> wrote:
> > On Fri, 2015-03-06 at 10:00 -0500, Steven Rostedt wrote:
> >> On Fri, 06 Mar 2015 15:18:42 +1100
> >> Benjamin Herrenschmidt wrote:
> >>
> >>
> >> > Can you shoot me the
From: Dan Carpenter
The indenting makes it clear that there were curly braces intended here.
Fixes: 2dd37cb81580 ('Drivers: hv: vmbus: Handle both rescind and offer
messages in the same context')
Signed-off-by: Dan Carpenter
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel_mgmt.c |
Export the vmbus_sendpacket_pagebuffer_ctl() interface.
Signed-off-by: K. Y. Srinivasan
---
drivers/hv/channel.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/hv/channel.c b/drivers/hv/channel.c
index da53180..e58cdb7 100644
--- a/drivers/hv/channel.c
+++
From: Vitaly Kuznetsov
Memory blocks can be onlined in random order. When this order is not natural
some memory pages are not onlined because of the redundant check in
hv_online_page().
Here is a real world scenario:
1) Host tries to hot-add the following (process_hot_add):
From: Vitaly Kuznetsov
When add_memory() fails the following BUG is observed:
[ 743.646107] hv_balloon: hot_add memory failed error is -17
[ 743.679973]
[ 743.680930] =
[ 743.680930] [ BUG: bad unlock balance detected! ]
[ 743.680930]
From: Nick Meier
HV_CRASH_CTL_CRASH_NOTIFY is a 64 bit number. Depending on the usage context,
the value may be truncated. This patch is in response from the following
email from Intel:
[char-misc:char-misc-testing 25/45] drivers/hv/vmbus_drv.c:67:9: sparse:
constant
This patch-set has miscellaneous fixes for both the VMBUS as well as the balloon
driver.
Dan Carpenter (1):
hv: vmbus: missing curly braces in vmbus_process_offer()
K. Y. Srinivasan (2):
Drivers: hv: vmbus: Export the vmbus_sendpacket_pagebuffer_ctl()
Drivers: hv: vmbus: Perform device
This patch is a continuation of the rescind handling cleanup work. We cannot
block in the global message handling work context especially if we are blocking
waiting for the host to wake us up. I would like to thank
Dexuan Cui for observing this problem.
Signed-off-by: K. Y. Srinivasan
---
On Sat, 2015-03-07 at 11:39 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 11:17 AM, Jason Low wrote:
> > On Sat, 2015-03-07 at 11:08 +0800, Ming Lei wrote:
> >> On Sat, Mar 7, 2015 at 10:56 AM, Jason Low wrote:
> >> > On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
> >> >> On Sat, Mar 7,
On Sat, 2015-03-07 at 11:19 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 11:10 AM, Davidlohr Bueso wrote:
> > On Sat, 2015-03-07 at 10:55 +0800, Ming Lei wrote:
> >> On Sat, Mar 7, 2015 at 10:29 AM, Davidlohr Bueso wrote:
> >> > On Fri, 2015-03-06 at 18:26 -0800, Davidlohr Bueso wrote:
> >>
On Sat, Mar 7, 2015 at 11:17 AM, Jason Low wrote:
> On Sat, 2015-03-07 at 11:08 +0800, Ming Lei wrote:
>> On Sat, Mar 7, 2015 at 10:56 AM, Jason Low wrote:
>> > On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
>> >> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso
>> >> wrote:
>> >> > On
As I did prior to the linux-3.0 release, I've created a commemorative tarball
of all stable point releases from linux 1.0 to linux 3.19 to commemorate the
upcoming 4.0 release, excluding minor point releases.
http://ck.kolivas.org/linux-1.0-3.19.tar.lrz
This was a 29GB tarball compressed to
Hi Antoine,
On 03/05/2015 08:31 AM, Antoine Tenart wrote:
[..]
> +
> +static struct pxa3xx_nand_flash berlin_builtin_flash_types[] = {
> +{ "4GiB 8-bit",0xd7ec, 128, 8192, 8, 8, 4096 },
> +{ },
IMHO, supporting a specific flash shouldn't be part of this patch.
In any case, why do you
On Sat, Mar 7, 2015 at 11:10 AM, Davidlohr Bueso wrote:
> On Sat, 2015-03-07 at 10:55 +0800, Ming Lei wrote:
>> On Sat, Mar 7, 2015 at 10:29 AM, Davidlohr Bueso wrote:
>> > On Fri, 2015-03-06 at 18:26 -0800, Davidlohr Bueso wrote:
>> >> That's not what this is about. New lock _owners_ need to
On Sat, 2015-03-07 at 11:08 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 10:56 AM, Jason Low wrote:
> > On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
> >> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
> >> > On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
> >> >> On Fri, 06
On Wed, Mar 04, 2015 at 08:32:54PM +0100, Arnd Bergmann wrote:
> This is my final piece of the puzzle for ARMv6/v7 multiplatform
> support. In combination with the other patches that are now
> at git://kernel.org/pub/scm/linux/kernel/git/arnd/playground.git
> multiplatform-4.0-rc2 and the at91 and
On Sat, 2015-03-07 at 11:08 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 10:56 AM, Jason Low wrote:
> > On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
> >> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
> >> > On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
> >> >> On Fri, 06
On Sat, 2015-03-07 at 10:55 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 10:29 AM, Davidlohr Bueso wrote:
> > On Fri, 2015-03-06 at 18:26 -0800, Davidlohr Bueso wrote:
> >> That's not what this is about. New lock _owners_ need to worry about
> >
On Sat, Mar 7, 2015 at 10:56 AM, Jason Low wrote:
> On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
>> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
>> > On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
>> >> On Fri, 06 Mar 2015 14:15:37 -0800
>> >> Davidlohr Bueso wrote:
>> >>
You only hit the silicon bug if you bombard the uart with characters
and simultaneously request a baud rate or framing change.
I'm not sure why you would do either to the uart console. Is it
possible your host machine is doing something weird?
If you have the leverage, remind the SoC vendor to
On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
> > On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
> >> On Fri, 06 Mar 2015 14:15:37 -0800
> >> Davidlohr Bueso wrote:
> >>
> >> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
On Sat, Mar 7, 2015 at 10:29 AM, Davidlohr Bueso wrote:
> On Fri, 2015-03-06 at 18:26 -0800, Davidlohr Bueso wrote:
>> That's not what this is about. New lock _owners_ need to worry about
> ^^^ make that "need not"
Sorry, could you explain a
In order to facilitate some clocksource validation,
add a max_cycles entry to the structure which will
hold the maximum cycle value that can safely be
multiplied without potentially causing an overflow.
Cc: Dave Jones
Cc: Linus Torvalds
Cc: Thomas Gleixner
Cc: Richard Cochran
Cc: Prarit
So Ingo asked me to resend this series, which is the result of
earlier discussions with Linus and his suggestions around
improvements to clocksource validation in the hope we can more
easily catch bad hardware.
There's also a few cleanups Linus suggested as well as a few I've been
meaning to get
The previous clocks_calc_max_nsecs had some unecessarily
complex bit logic to find the max interval that could cause
multiplication overflows. Since this is not in the hot
path, just do the divide to make it easier to read.
The previous implementation also had a subtle issue
that it avoided
clocksource_max_deferment() doesn't do anything useful
anymore, so zap it.
Cc: Dave Jones
Cc: Linus Torvalds
Cc: Thomas Gleixner
Cc: Richard Cochran
Cc: Prarit Bhargava
Cc: Stephen Boyd
Cc: Ingo Molnar
Cc: Peter Zijlstra
Signed-off-by: John Stultz
---
kernel/time/clocksource.c | 20
When calculating the current delta since the last tick, we
currently have no hard protections to prevent a multiplciation
overflow from ocurring.
This patch introduces infrastructure to allow a capp that
limits the read delta value to the max_cycles value, which is
where an overflow would occur.
The clocksource watchdog reporting has been less helpful
then desired, as it just printed the delta between
the two clocksources. This prevents any useful analysis
of why the skew occurred.
Thus this patch tries to improve the output when we
mark a clocksource as unstable, printing out the cycle
It was suggested that the underflow/overflow protection
should probably throw some sort of warning out, rather
then just silently fixing the issue.
So this patch adds some warnings here. The flag variables
used are not protected by locks, but since we can't print
from the reading functions, just
This adds i2c_imc, a driver for the SMBUS lines on DIMM slots on modern
Intel server chips. Conceptually, I like it a lot -- it's a driver for
a bus for which we know the exact topology a priori. That means that we
can actually enumerate the things on the bus reasonably cleanly.
This driver is
While cleaning up some clocksource code, I noticed the
time_32 impelementation uses the hz2mult helper, but
doesn't use the clocksource_register_hz() method.
I don't believe the sparc clocksource is a default
clocksource, so we shouldn't need to self-define
the mult/shift pair.
So convert the
Recently there's been some request for better sanity
checking in the time code, so that its more clear
when something is going wrong since timekeeping issues
could manifest in a large number of strange ways with
various subsystems.
Thus, this patch adds some extra infrastructure to
add a check
Add i2c_scan_dimm_bus to declare that a particular i2c_adapter
contains DIMMs. This will probe (and autoload modules!) for useful
SMBUS devices that live on DIMMs. i2c_imc calls it.
As more SMBUS-addressable DIMM components become supported, this
code can be extended to probe for them.
Sandy Bridge Xeon and Extreme chips have integrated memory
controllers with (rather limited) onboard SMBUS masters. This
driver gives access to the bus.
There are various groups working on standardizing a way to arbitrate
access to the bus between the OS, SMM firmware, a BMC, hardware
thermal
Print the mask, max_cycles, and max_idle_ns values for clocksources
being registered.
Cc: Dave Jones
Cc: Linus Torvalds
Cc: Thomas Gleixner
Cc: Richard Cochran
Cc: Prarit Bhargava
Cc: Stephen Boyd
Cc: Ingo Molnar
Cc: Peter Zijlstra
Signed-off-by: John Stultz
---
A long running project has been to cleanup remaining uses
of clocksource_register(), replacing it with the simpler
clocksource_register_khz/hz().
However, there are a few cases where we need to self-define
our mult/shift values, so switch the function to a more
obviously internal
In the case where there is a broken clocksource
where there are multiple actual clocks that
aren't perfectly aligned, we may see small "negative"
deltas when we subtract now from cycle_last.
The values are actually negative with respect to the
clocksource mask value, not necessarily negative
if
The clocksource logic has a number of places where we try to
include a safety margin. Most of these are 12% safety margins,
but they are inconsistently applied and sometimes are applied
on top of each other.
Additionally, in the previous patch, we corrected an issue
where we unintentionally in
Liebe Begünstigte,
Sie wurden ausgewählt, um (€ 950.000,00 EURO) als Charity-Spenden / Hilfe der
Qatar Foundation erhalten. Kontaktieren Sie uns über E-Mail für weitere
Informationen;
Mit freundlichen Grüßen,
Ingenieur Saad Al Muhannadi.
Kontakt e-mail: qatarfoundationinternatio...@gmail.com
From: Andi Kleen
Fix regression caused by 85c116a6cb
We did not print the IP anymore for perf script -o ip, but instead
symbol+offset, and if there was no symbol only +offset.
Print the raw IP correctly again in this case.
Reported-by: Yuanfang Chen
Cc: Yuanfang Chen
Signed-off-by: Andi
On Fri, 2015-03-06 at 18:26 -0800, Davidlohr Bueso wrote:
> That's not what this is about. New lock _owners_ need to worry about
^^^ make that "need not"
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Sat, 2015-03-07 at 10:10 +0800, Ming Lei wrote:
> On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
> > On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
> >> On Fri, 06 Mar 2015 14:15:37 -0800
> >> Davidlohr Bueso wrote:
> >>
> >> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
On Sat, Mar 7, 2015 at 10:07 AM, Davidlohr Bueso wrote:
> On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
>> On Fri, 06 Mar 2015 14:15:37 -0800
>> Davidlohr Bueso wrote:
>>
>> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
>> > > In owner_running() there are 2 conditions that would
I wrote a kernel module that sends generic Netlink multicasts, and
wrote a userland client using libmnl that receives them.
That all works fine, but my client works even when it's not the root user.
man 7 netlink says:
Only processes with an effective UID of 0 or the CAP_NET_ADMIN capability
On Sat, 2015-03-07 at 09:55 +0800, Ming Lei wrote:
> On Fri, 06 Mar 2015 14:15:37 -0800
> Davidlohr Bueso wrote:
>
> > On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> > > In owner_running() there are 2 conditions that would make it return
> > > false: if the owner changed or if the owner
On Fri, 2015-03-06 at 14:15 -0800, Davidlohr Bueso wrote:
> On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> > In owner_running() there are 2 conditions that would make it return
> > false: if the owner changed or if the owner is not running. However,
> > that patch continues spinning if
On Fri, 06 Mar 2015 14:15:37 -0800
Davidlohr Bueso wrote:
> On Fri, 2015-03-06 at 13:12 -0800, Jason Low wrote:
> > In owner_running() there are 2 conditions that would make it return
> > false: if the owner changed or if the owner is not running. However,
> > that patch continues spinning if
On Fri, 2015-03-06 at 13:24 -0800, Linus Torvalds wrote:
> On Fri, Mar 6, 2015 at 1:12 PM, Jason Low wrote:
> >
> > + while (true) {
> > + if (sem->owner != owner)
> > + break;
>
> That looks *really* odd.
>
> Why is this not
>
> while
The change:
75182b1632a8 x86/asm/entry: Switch all C consumers of kernel_stack to
this_cpu_sp0()
had the unintended side effect of changing the return value of
current_thread_info() during part of the context switch process.
Change it back.
This has no effect as far as I can tell -- it's just
I broke 32-bit kernels. The implementation of sp0 was correct as
far as I can tell, but sp0 was much weirder on x86_32 than I
realized. It has the following issues:
- Init's sp0 is inconsistent with everything else's: non-init tasks
are offset by 8 bytes. (I have no idea why, and the
I broke x86_32 and I made an inadvertent change to both bitnesses.
Undo the inadvertent change and fix x86_32.
This isn't as pretty as I hoped. Sorry.
Andy Lutomirski (2):
x86: Delay loading sp0 slightly on task switch
x86: Replace this_cpu_sp0 with current_top_of_stack and fix it on
On Fri, Mar 06, 2015 at 11:37:45AM -0700, Ross Zwisler wrote:
> Regarding the PMEM series, my group has been working on an updated
> version of this driver for the past 6 months or so since I initially
> posted the beginnings of this series:
>
> https://lkml.org/lkml/2014/8/27/674
>
> That new
On Fri, Mar 06, 2015 at 05:03:00PM -0800, Davidlohr Bueso wrote:
> On Fri, 2015-03-06 at 16:37 -0800, Paul E. McKenney wrote:
> > On Sat, Mar 07, 2015 at 03:06:53AM +0300, Alexey Kodanev wrote:
> > > torture_rwlock_read_unlock_irq() must use read_unlock_irqrestore()
> > > instead of
Hi,
This adds (long in coming) support for the Broadcom BCM7xxx Set-Top Box NAND
controller. This controller has been used in a variety of Broadcom SoCs.
There are a few more features I'd like add in the near future, mostly to
support more SoCs, but this is the base set, which should only need
This core originated in Set-Top Box chips (BCM7xxx) but is used in a
variety of other Broadcom chips, including some BCM63xxx, BCM33xx, and
iProc/Cygnus. It's been used only on ARM and MIPS SoCs, so restrict it
to those architectures.
There are multiple revisions of this core throughout the
These are already-documented common bindings for NAND chips. Let's
handle them in nand_base.
If NAND controller drivers need to act on this data before bringing up
the NAND chip (e.g., fill out ECC callback functions, change HW modes,
etc.), then they can do so between calling nand_scan_ident()
Signed-off-by: Brian Norris
---
.../devicetree/bindings/mtd/brcmstb_nand.txt | 109 +
1 file changed, 109 insertions(+)
create mode 100644 Documentation/devicetree/bindings/mtd/brcmstb_nand.txt
diff --git a/Documentation/devicetree/bindings/mtd/brcmstb_nand.txt
* Rafael J. Wysocki [150306 16:19]:
> On Friday, March 06, 2015 03:05:40 PM Tony Lindgren wrote:
> >
> > Oh it naturally would not work in irq context, it's for the bottom
> > half again. But I'll take a look if we can just call
> > pm_request_resume() and disable_irq() on the wakeirq in without
Add the missing toshiba_bluetooth and toshiba_haps entries and add
myself as their maintainer.
Also add the Maintainers entry for toshiba_acpi driver and change its
status to maintained.
Signed-off-by: Azael Avalos
---
MAINTAINERS | 15 ++-
1 file changed, 14 insertions(+), 1
This patch adds a few more events sent to TOS devices, some of
them are already identified, while some others simply print a message
informing the type of event received.
Also, a netlink event is generated so that userspace apps, daemons,
etc. act accordingly to these events.
Signed-off-by:
On Wed, 4 Mar 2015 15:48:24 -0500
Steven Rostedt wrote:
> On Wed, 4 Mar 2015 21:33:16 +0100
> Ingo Molnar wrote:
>
> >
> > * Alexei Starovoitov wrote:
> >
> > > On Sun, Mar 1, 2015 at 3:27 PM, Alexei Starovoitov
> > > wrote:
> > > > Peter, Steven,
> > > > I think this set addresses
On Tue, Mar 03, 2015 at 09:44:06AM +, Mark Brown wrote:
> On Mon, Mar 02, 2015 at 06:28:43PM +0100, Geert Uytterhoeven wrote:
> > The r8a7791/koelsch development board has da9063 and da9210 regulators.
> > Both regulators have their interrupt request lines tied to the same
> > interrupt pin
On Fri, 2015-03-06 at 16:37 -0800, Paul E. McKenney wrote:
> On Sat, Mar 07, 2015 at 03:06:53AM +0300, Alexey Kodanev wrote:
> > torture_rwlock_read_unlock_irq() must use read_unlock_irqrestore()
> > instead of write_unlock_irqrestore().
> >
> > Use read_unlock_irqrestore() instead of
On Fri, 6 Mar 2015 10:34:42 +0800
wrote:
> From: Yanjiang Jin
>
> Fix rng_unmap_ctx's DMA_UNMAP size problem for caam_rng, else system would
> report the below calltrace during cleanup caam_rng.
> Since rng_create_sh_desc() creates a fixed descriptor of exactly 4
> command-lengths now, also
On Wed, 2015-03-04 at 23:45 -0600, Emil Medve wrote:
> From: Igal Liberman
>
> Signed-off-by: Igal Liberman
> ---
> drivers/soc/Kconfig |1 +
> drivers/soc/Makefile |1 +
> drivers/soc/fsl/Kconfig |1 +
> drivers/soc/fsl/Makefile |1 +
>
On Fri, Mar 06, 2015 at 10:21:55AM -0800, Dmitry Torokhov wrote:
> On Fri, Mar 06, 2015 at 07:21:38PM +0100, Sébastien Szymanski wrote:
> > Signed-off-by: Sébastien Szymanski
> > ---
> > drivers/input/touchscreen/Kconfig | 11 ++
> > drivers/input/touchscreen/Makefile | 1 +
> >
On Fri, Mar 6, 2015 at 11:56 AM, Kees Cook wrote:
> On Fri, Mar 6, 2015 at 11:28 AM, Yinghai Lu wrote:
> Okay, I've proven this to myself now. :) I think it would be valuable
> to call out that brk and bss are included in the _end calculation. For
> others:
...
> So, _end - _text does equal
The current cryptodev-2.6 tree commits:
d9850fc529ef ("crypto: powerpc/sha1 - kernel config")
50ba29aaa7b0 ("crypto: powerpc/sha1 - glue")
failed to properly place files under arch/powerpc/crypto, which
leads to build errors:
make[1]: *** No rule to make target
On Fri, 6 Mar 2015 10:34:41 +0800
wrote:
> From: Yanjiang Jin
>
> sec4_sg_bytes not being properly initialized causes ahash_done
> to try to free unallocated DMA memory:
>
> caam_jr ffe301000.jr: DMA-API: device driver tries to free DMA memory it has
> not allocated [device
On Sat, Mar 07, 2015 at 03:06:53AM +0300, Alexey Kodanev wrote:
> torture_rwlock_read_unlock_irq() must use read_unlock_irqrestore()
> instead of write_unlock_irqrestore().
>
> Use read_unlock_irqrestore() instead of write_unlock_irqrestore().
>
> Signed-off-by: Alexey Kodanev
Good catch! If
1 - 100 of 1860 matches
Mail list logo
