On 5/28/2014 4:04 PM, Dann Frazier wrote:
On Thu, May 1, 2014 at 1:04 PM, Murali Karicheri wrote:
8250 uart driver currently supports only software assisted hw flow
control. The software assisted hw flow control maintains a hw_stopped
flag in the tty structure to stop and start transmission
On Wed, 2014-06-11 at 07:55 +0300, Johan Hedberg wrote:
> Hi,
>
> On Tue, Jun 10, 2014, Kamal Mostafa wrote:
> > 3.13.11.3 -stable review patch. If anyone has any objections, please let
> > me know.
> >
> > --
> >
> > From: Johan Hedberg
> >
> > commit
On Tue, 2014-06-10 at 15:49 +0300, Dmitry Kasatkin wrote:
> On 10/06/14 15:45, Mimi Zohar wrote:
> > On Tue, 2014-06-10 at 11:48 +0300, Dmitry Kasatkin wrote:
> >> Hi Mimi,
> >>
> >> As you asked ofline , here is possible equivalent and simpler alternative
> >> patches not requiring to have
Dave Chiluk writes:
> On 06/11/2014 11:18 AM, Paul E. McKenney wrote:
>> On Wed, Jun 11, 2014 at 10:46:00AM -0500, David Chiluk wrote:
>>> Now think about what happens when a gateway goes down, the namespaces
>>> need to be migrated, or a new machine needs to be brought up to replace
>>> it.
While looking for the minimal functional fix for the futex CVE, I
found a few things which can be done simpler and therefor make the
code more robust.
1) UNLOCK_PI
Change the ordering:
- Lookup waiters first. If waiters exist wake up the top priority
waiter with all sanity checks
No point in open coding the same function again.
Signed-off-by: Thomas Gleixner
---
kernel/futex.c | 128 -
1 file changed, 63 insertions(+), 65 deletions(-)
Index: linux/kernel/futex.c
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the waiter verification into a separate
function. No functional change.
Signed-off-by: Thomas Gleixner
---
kernel/futex.c | 138 +
1
The kernel tries to atomically unlock the futex without checking
whether there is kernel state associated to the futex.
So if user space manipulated the user space value, this will leave
kernel internal state around associated to the owner task.
For robustness sake, lookup first whether there
On Wed, 11 Jun 2014, Julia Lawall wrote:
> > > v2: pass correct arguments to devm_ioremap_resource
> > > Not compile tested due to incompatible architecture.
> >
> > uhci-platform is compatible with all architectures. But you have to
> > add it to the .config file by hand.
>
> What should one
Il giorno 04/giu/2014, alle ore 13:59, Takashi Iwai ha scritto:
> […]
> I've been using BFQ for a while and noticed also some obvious
> regression in some operations, notably git, too.
> For example, git grep regresses badly.
>
> I ran "test git grep foo > /dev/null" on linux kernel repos on
futex_lock_pi_atomic() is a maze of retry hoops and loops.
Reduce it to simple and understandable states:
First step is to lookup existing waiters (state) in the kernel.
If there is an existing waiter, validate it and attach to it.
If there is no existing waiter, check the user space value
If
We want to be a bit more clever in futex_lock_pi_atomic() and separate
the possible states. Split out the code which attaches the first
waiter to the owner into a separate function. No functional change.
Signed-off-by: Thomas Gleixner
---
kernel/futex.c | 42
Am Montag, 9. Juni 2014, 15:17:25 schrieb Dirk Brandewie:
>
> Hi Martin,
>
> Can you send the output of:
> turbostat sleep 10
> and
> for i in 0 1 2 3; do rdmsr -p $i -u -f15:8 0x198; done
>
> For the normal and bad case please.
Okay, here we have the bad, bad case – see other mail
Is this accepted?
On Tue, Jun 10, 2014 at 11:41:33PM +0200, Rafael J. Wysocki wrote:
> On Tuesday, June 10, 2014 05:17:16 PM Steven Rostedt wrote:
> > On Tue, 10 Jun 2014 23:17:46 +0200
> > "Rafael J. Wysocki" wrote:
> >
> > > On Tuesday, June 10, 2014 07:31:22 AM Todd E Brandt wrote:
> > > >
On 06/11/2014 12:25 PM, Theodore Ts'o wrote:
> On Wed, Jun 11, 2014 at 09:48:31AM -0700, H. Peter Anvin wrote:
>> While talking about performance, I did a quick prototype of random using
>> Skein instead of SHA-1, and it was measurably faster, in part because
>> Skein produces more output per
Il giorno 04/giu/2014, alle ore 12:03, Pavel Machek ha scritto:
> Hi!
>
>> Should this attempt be useless as well, I will, if you do not mind, try by
>> asking you more details about your system and reproducing your configuration
>> as much as I can.
>>
>
> Try making BFQ the default
The following patch series fixes sparse warning. There are still 3 warnings left
which I am figuring out. I wanted to send these to get feedback and see if I am
on the right path.
Patch 1 is the significant one which involves some refactoring. I am guessing
the 3 remaining sparse warnings will
kernel/rcu/tree.c:1272:9: warning: context imbalance in 'rcu_start_future_gp' -
different lock contexts for basic block
We can simplify the function by keeping the contexts together and removing
redundant checks.
Signed-off-by: Pranith Kumar
---
kernel/rcu/tree.c | 65
kernel/rcu/tree_plugin.h:990:13: warning: context imbalance in
'rcu_report_unblock_qs_rnp' - unexpected unlock
by annotating the function with __releases()
Signed-off-by: Pranith Kumar
---
kernel/rcu/tree_plugin.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/kernel/rcu/tree_plugin.h
kernel/rcu/tree_plugin.h:1494:13: warning: context imbalance in
'rcu_initiate_boost' - unexpected unlock
by annotating the function with releases()
Signed-off-by: Pranith Kumar
---
kernel/rcu/tree_plugin.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/rcu/tree_plugin.h
kernel/rcu/tree.c:3435:21: warning: incorrect type in argument 1 (different
modifiers)
kernel/rcu/tree.c:3435:21:expected int ( *threadfn )( ... )
kernel/rcu/tree.c:3435:21:got int ( static [toplevel] [noreturn] *
)( ... )
by removing __noreturn attribute and adding unreachable() as
fix the following sparse warning
kernel/rcu/rcutorture.c:185:1: warning: symbol 'boost_mutex' was not declared.
Should it be static?
by marking boost_mutex as a static mutex
Signed-off-by: Pranith Kumar
---
kernel/rcu/rcutorture.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Am Montag, 9. Juni 2014, 15:17:25 schrieb Dirk Brandewie:
> Hi Martin,
Hi Dirk,
> Can you send the output of:
> turbostat sleep 10
> and
> for i in 0 1 2 3; do rdmsr -p $i -u -f15:8 0x198; done
>
> For the normal and bad case please.
Normal case:
merkaba:~> turbostat sleep 10
On Wed 11-06-14 10:55:55, Sasha Levin wrote:
> On 06/10/2014 11:59 AM, Peter Hurley wrote:
> > On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >> On 05/30/2014 10:07 AM, Jan Kara wrote:
> >>> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> > On 05/30/2014 09:11 AM, Sasha Levin wrote:
> >>> Hi
Driver for the native I2C adapter found in Rockchip RK3xxx SoCs.
Configuration is only possible through devicetree. The driver is
interrupt driven and supports the I2C_M_IGNORE_NAK mangling bit.
Signed-off-by: Max Schwarz
---
The driver cannot be used without a proper clock driver
supporting
On Wed 11-06-14 11:34:28, Peter Hurley wrote:
> On 06/11/2014 10:55 AM, Sasha Levin wrote:
> >On 06/10/2014 11:59 AM, Peter Hurley wrote:
> >>On 06/06/2014 03:05 PM, Sasha Levin wrote:
> >>>On 05/30/2014 10:07 AM, Jan Kara wrote:
> On Fri 30-05-14 09:58:14, Peter Hurley wrote:
> >>On
Eyal, the commit you reference below isn't anywhere to be found in
Linus's tree. Why is this commit needed at all if that one isn't there
either?
Confused,
greg k-h
On Sun, Jun 08, 2014 at 06:59:19PM +, Linux Kernel Mailing List wrote:
> Gitweb:
>
Hi Wolfram,
thanks for your comments.
On Tuesday 10 June 2014 at 21:27:09, Wolfram Sang wrote:
> Checking if the spinlock is needed would be nice, but we can also fix
> this later.
I'm simply not sure about the spinlock. My knowledge about IRQ handling in
linux is limited.
We have an SMP
The secure_computing function took a syscall number parameter, but
it only paid any attention to that parameter if seccomp mode 1 was
enabled. Rather than coming up with a kludge to get the parameter
to work in mode 2, just remove the parameter.
To avoid churn in arches that don't have seccomp
On Tue, Jun 10, 2014 at 4:11 AM, Thierry Reding
wrote:
> From: Thierry Reding
>
> The XUSB pad controller found on NVIDIA Tegra SoCs provides several pads
> that lanes can be assigned to in order to support a variety of interface
> options: USB 2.0, USB 3.0, PCIe and SATA.
>
> In addition to the
The reason I did this is to add a seccomp API that will be usable
for an x86 fast path. The x86 entry code needs to use a rather
expensive slow path for a syscall that might be visible to things
like ptrace. By splitting seccomp into two phases, we can check
whether we need the slow path and
For slowpath syscalls, we initialize regs->ax to -ENOSYS and stick
the syscall number into regs->orig_ax prior to any possible tracing
and syscall execution. This is user-visible ABI used by ptrace
syscall emulation and seccomp.
For fastpath syscalls, there's no good reason not to do the same
On my VM, getpid takes about 70ns. Before this patch, adding a
single-instruction always-accept seccomp filter added about 134ns of
overhead to getpid. With this patch, the overhead is down to about
13ns.
I'm not really thrilled by this patch. It has two main issues:
1. Calling into code in
Signed-off-by: Andy Lutomirski
---
include/linux/seccomp.h | 2 +-
kernel/seccomp.c| 32 +++-
2 files changed, 20 insertions(+), 14 deletions(-)
diff --git a/include/linux/seccomp.h b/include/linux/seccomp.h
index 8345fdc..4fc7a84 100644
---
On my VM, getpid takes about 70ns. Before this patchset, adding a
single-instruction always-accept seccomp filter added about 134ns of
overhead to getpid. With this patchset, the overhead is down to about
13ns.
I'd really appreciate careful review from all relevant arch
maintainers for patch 1.
On Wed, Jun 11, 2014 at 2:37 PM, Rob Clark wrote:
> On Thu, May 29, 2014 at 2:36 AM, Benjamin Gaignard
> wrote:
>> This series of patches add the support of DRM/KMS drivers for
>> STMicroelectronics
>> chipsets stih416 and stih407.
>>
>> version 4:
>> - Remove depency between TVout it
On 11/06/2014 06:02 μμ, Doug Smythies wrote:
>
> On 2104.06.11 07:08 Stratos Karafotis wrote:
>> On 11/06/2014 04:41 μμ, Doug Smythies wrote:
>>
>> No.
>>
>> The intent was only ever to round properly the pseudo floating point result
>> of the divide.
>> It was much more important (ugh, well 4
Signed-off-by: Franck Jullien
---
drivers/video/fbdev/Kconfig |2 ++
drivers/video/fbdev/ocfb.c | 31 ++-
2 files changed, 28 insertions(+), 5 deletions(-)
diff --git a/drivers/video/fbdev/Kconfig b/drivers/video/fbdev/Kconfig
index e1f4727..b4ac6bb 100644
---
I'm seeing this build failure for arm64:
CC [M] Documentation/filesystems/configfs/configfs_example_macros.o
In file included from /usr/include/bits/sigcontext.h:27:0,
from /usr/include/signal.h:340,
from /usr/include/sys/wait.h:30,
On Thu, May 29, 2014 at 2:37 AM, Benjamin Gaignard
wrote:
> Make the link between all the hardware drivers and DRM/KMS interface.
> Create the driver itself and make it register all the sub-components.
> Use GEM CMA helpers for buffer allocation.
>
> Signed-off-by: Benjamin Gaignard
> ---
>
On 6/11/14, Catalin Marinas wrote:
> On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote:
>> I got a trace while running 3.15.0-08556-gdfb9454:
>>
>> [ 104.534026] Unable to handle kernel paging request for data at
>> address 0xc0007f00
>
> Were there any kmemleak messages
On Wed, Jun 11, 2014 at 07:59:34PM +0200, Oleg Nesterov wrote:
> On 06/11, Paul E. McKenney wrote:
> >
> > On Wed, Jun 11, 2014 at 07:17:34PM +0200, Oleg Nesterov wrote:
> > > On 06/11, Oleg Nesterov wrote:
> > > >
> > > > On 06/11, Paul E. McKenney wrote:
> > > >
> > > > >
unsigned value is never < 0
Cc: Jean-Christophe Plagniol-Villard
Cc: Tomi Valkeinen
Signed-off-by: Fabian Frederick
---
drivers/video/fbdev/sis/sis_main.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/video/fbdev/sis/sis_main.c
b/drivers/video/fbdev/sis/sis_main.c
index
On Tue, Jun 03, 2014 at 03:41:56PM -0400, Jérôme Carretero wrote:
> This vendor has similar boards based on the same Marvell 88SE9235 chipset,
> but this patch was only tested with the 642L.
>
> Tested on ASUS Sabertooth 990FX (AMD).
>
> If you listen to the vendor support stating:
>
> Dear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.12.22 kernel.
All users of the 3.12 kernel series must upgrade.
The updated 3.12.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.12.y
and can be
I'm announcing the release of the 3.14.7 kernel.
All users of the 3.14 kernel series must upgrade.
The updated 3.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.14.y
and can be browsed at the normal kernel.org git web browser:
I'm announcing the release of the 3.4.93 kernel.
All users of the 3.4 kernel series must upgrade.
The updated 3.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Documentation/DocBook/media/Makefile
b/Documentation/DocBook/media/Makefile
index f9fd615427fb..1d27f0a1abd1 100644
--- a/Documentation/DocBook/media/Makefile
+++ b/Documentation/DocBook/media/Makefile
@@ -195,7 +195,7 @@ DVB_DOCUMENTED = \
#
install_media_images = \
-
I'm announcing the release of the 3.10.43 kernel.
All users of the 3.10 kernel series must upgrade.
The updated 3.10.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.10.y
and can be browsed at the normal kernel.org git web
On Wed, Jun 11, 2014 at 01:27:07PM -0500, Dave Chiluk wrote:
> On 06/11/2014 11:18 AM, Paul E. McKenney wrote:
> > On Wed, Jun 11, 2014 at 10:46:00AM -0500, David Chiluk wrote:
> >> Now think about what happens when a gateway goes down, the namespaces
> >> need to be migrated, or a new machine
Hi Luis,
On Wed, Jun 11, 2014 at 07:46:44PM +0100, Luis Henriques wrote:
> Hi Willy,
>
> On Mon, May 12, 2014 at 02:32:59AM +0200, Willy Tarreau wrote:
> > 2.6.32-longterm review patch. If anyone has any objections, please let me
> > know.
> >
>
> During Ubuntu Lucid kernel regression
On Wed, Jun 11, 2014 at 12:44 PM, Sam Ravnborg wrote:
> On Wed, Jun 11, 2014 at 12:41:57PM -0700, Andy Lutomirski wrote:
>> Every few months, I forget why I type:
>>
>> $ sudo make -j12 modules_install && sudo make -j12 install
>>
>> instead of just:
>>
>> $ sudo make -j12 modules_install install
On Wed, Jun 11, 2014 at 12:25:29PM -0700, Andy Lutomirski wrote:
> The filenames are different now. Inspired by a patch from
> Sam Ravnborg.
>
> Reported-by: Josh Boyer
> Signed-off-by: Andy Lutomirski
Better than the first version - thanks!
Acked-by: Sam Ravnborg
Sam
--
To
On Wed, Jun 11, 2014 at 12:41:57PM -0700, Andy Lutomirski wrote:
> Every few months, I forget why I type:
>
> $ sudo make -j12 modules_install && sudo make -j12 install
>
> instead of just:
>
> $ sudo make -j12 modules_install install
>
> I try the latter, it appears to work, and then my
Acked-by: Dimitri Sivanich
On Wed, Jun 11, 2014 at 08:47:02PM +0200, Fabian Frederick wrote:
> unsigned value is never < 0
>
> Cc: Dimitri Sivanich
> Signed-off-by: Fabian Frederick
> ---
> drivers/misc/sgi-gru/grukdump.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff
Every few months, I forget why I type:
$ sudo make -j12 modules_install && sudo make -j12 install
instead of just:
$ sudo make -j12 modules_install install
I try the latter, it appears to work, and then my machine won't boot
because dracut got confused. This fixes it once and for all: if you
> > v2: pass correct arguments to devm_ioremap_resource
> > Not compile tested due to incompatible architecture.
>
> uhci-platform is compatible with all architectures. But you have to
> add it to the .config file by hand.
What should one do exactly? I added
CONFIG_USB_UHCI_PLATFORM=y
to the
On Wed, Jun 11, 2014 at 11:29:57AM +0800, Peter Chen wrote:
> On Tue, Jun 10, 2014 at 11:35:07PM -0500, Felipe Balbi wrote:
> > Hi,
> >
> > On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> > > > Let's take USB peripheral as an example, there is a device for
> > > > udc, and a device
В Ср, 11/06/2014 в 17:43 +0400, Kirill Tkhai пишет:
>
> 11.06.2014, 17:15, "Srikar Dronamraju" :
> >>> * Kirill Tkhai [2014-06-11 13:52:10]:
> Currently migrate_tasks() skips throttled tasks,
> because they are not pickable by pick_next_task().
> >>> Before migrate_tasks() is
On Thu, 12 Jun 2014, Himangi Saraogi wrote:
> This patch replaces the memory allocation using request_mem_region and
> the ioremap by a single call to managed interface devm_ioremap_reource.
> The corresponding calls to release_mem_region and iounmap in the probe
> and release functions are now
On Wed, 11 Jun 2014, Greg KH wrote:
> We can't break existing systems, so I don't understand the issue here.
> Just don't configure your kernel for a system you don't have / want,
> right?
>
> > > > From what I read code, we can't implement above feature, but I may
> > > > be wrong, if you have
On Wed, Jun 11, 2014 at 09:48:31AM -0700, H. Peter Anvin wrote:
> While talking about performance, I did a quick prototype of random using
> Skein instead of SHA-1, and it was measurably faster, in part because
> Skein produces more output per hash.
Which Skein parameters did you use, and how
On Tue, Jun 10, 2014 at 06:31:28PM +0200, Borislav Petkov wrote:
[..]
> > diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> > index 213308a..0f24b61 100644
> > --- a/arch/x86/Kconfig
> > +++ b/arch/x86/Kconfig
> > @@ -1556,6 +1556,8 @@ source kernel/Kconfig.hz
> > config KEXEC
> > bool
The filenames are different now. Inspired by a patch from
Sam Ravnborg.
Reported-by: Josh Boyer
Signed-off-by: Andy Lutomirski
---
arch/x86/vdso/Makefile | 22 +++---
1 file changed, 11 insertions(+), 11 deletions(-)
diff --git a/arch/x86/vdso/Makefile
On Tue, 2014-06-03 at 15:41 -0400, Jérôme Carretero wrote:
> This vendor has similar boards based on the same Marvell 88SE9235 chipset,
> but this patch was only tested with the 642L.
>
> Tested on ASUS Sabertooth 990FX (AMD).
>
> If you listen to the vendor support stating:
>
> Dear
On Tue, Jun 10, 2014 at 04:13:04PM -0700, H. Peter Anvin wrote:
> After a recent problem in the x86 tree, which seems to be the heaviest
> but not the only user of these functions, I went through and did a
> patchset to revamp the *user space* unaligned/endian accessor
> functions. As much as I
This patch replaces the memory allocation using request_mem_region and
the ioremap by a single call to managed interface devm_ioremap_reource.
The corresponding calls to release_mem_region and iounmap in the probe
and release functions are now unnecessary and are removed. Also a label
is done away
On Wed, Jun 11, 2014 at 12:16 PM, Sam Ravnborg wrote:
>> >
>> > Can we please fix this in a way where we do not need to add stuff to core
>> > kbuild.
>> > If the original approach was used then make took care of the looping
>> > and the foreach part was not needed.
> Following is my first quick
Hi Laura,
On Wed, Jun 11, 2014 at 7:32 PM, Laura Abbott wrote:
> On 6/11/2014 4:40 AM, Geert Uytterhoeven wrote:
>> With current mainline, I get an early crash on r8a7791/koelsch:
>>
>> BUG: Bad page state in process swapper pfn:0
>> page:ee20b000 count:0 mapcount:0 mapping:66756200
> >
> > Can we please fix this in a way where we do not need to add stuff to core
> > kbuild.
> > If the original approach was used then make took care of the looping
> > and the foreach part was not needed.
Following is my first quick approach.
It reuses the old - a little complex logic to do
On Thu, May 29, 2014 at 2:37 AM, Benjamin Gaignard
wrote:
> Generic Display Pipeline are one of the compositor input sub-devices.
> GDP are dedicated to graphic input like RGB plans.
> GDP is part of Compositor hardware block which will be introduce later.
>
> A sti_layer structure is used to
Older kernels (e.g., RHEL6) do system call tracing via
syscalls:sys_{enter,exit} rather than raw_syscalls.
Update perf-scripts to fallback to syscalls in the
lack of raw_syscall support.
Signed-off-by: Daniel Bristot de Oliveira
---
tools/perf/scripts/perl/bin/failed-syscalls-record |
On Wed, Jun 11, 2014 at 11:23:23AM +0800, Peter Chen wrote:
> On Tue, Jun 10, 2014 at 09:10:00PM -0700, Greg KH wrote:
> > On Wed, Jun 11, 2014 at 10:14:40AM +0800, Peter Chen wrote:
> > > Hi Greg,
> > >
> > > Currently, we can't disable auto probe function during booting
> > > if both device and
If CONFIG_PM_SLEEP=n:
drivers/input/keyboard/st-keyscan.c:219: warning: ‘keyscan_suspend’ defined but
not used
drivers/input/keyboard/st-keyscan.c:236: warning: ‘keyscan_resume’ defined but
not used
Signed-off-by: Geert Uytterhoeven
---
drivers/input/keyboard/st-keyscan.c | 2 ++
1 file
On Thu, May 29, 2014 at 2:37 AM, Benjamin Gaignard
wrote:
> Mixer hardware IP is responsible of mixing the different inputs layers.
> Z-order is managed by the mixer.
> We could 2 mixers: one for main path and one for auxillary path
>
> Mixers are part of Compositor hardware block
>
>
On Wed, Jun 11, 2014 at 11:51 AM, Sam Ravnborg wrote:
> On Wed, Jun 11, 2014 at 01:23:59PM -0400, Josh Boyer wrote:
>> On Wed, Jun 11, 2014 at 12:20 PM, Andy Lutomirski
>> wrote:
>> > Rather than monkeying with barely-comprehensible static pattern
>> > rules, just use an explicit loop.
>> >
>>
If CONFIG_PM=n:
drivers/hid/hid-rmi.c:432: warning: ‘rmi_post_reset’ defined but not used
drivers/hid/hid-rmi.c:437: warning: ‘rmi_post_resume’ defined but not used
Signed-off-by: Geert Uytterhoeven
---
drivers/hid/hid-rmi.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On Mon, Jun 2, 2014 at 7:45 PM, Emil Goode wrote:
> The variable err is not initialized here, this patch uses it
> to store an eventual error value from devm_clk_get().
>
> Signed-off-by: Emil Goode
Acked-by: Geert Uytterhoeven
Gr{oetje,eeting}s,
Geert
--
Geert
On Wed, Jun 11, 2014 at 04:34:49AM -0400, Chen, Gong wrote:
> Add trace interface to elaborate all H/W error related information.
>
> v7 -> v6: compact trace info to save trace buffer space.
> v6 -> v5: format adjustment.
> v5 -> v4: Add physical mask(LSB) in trace.
> v4 -> v3: change ras trace
On 06/11/14 01:37, Xiubo Li wrote:
> The third parameter(u64 start_tstamp) of timecounter_init() should
> be the start time by ns, not a cycle counter.
>
> Signed-off-by: Xiubo Li
> ---
> drivers/clocksource/arm_arch_timer.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff
On Wed, Jun 11, 2014 at 11:44 AM, Sam Ravnborg wrote:
> On Wed, Jun 11, 2014 at 12:41:56PM -0400, Josh Boyer wrote:
>> On Wed, Jun 11, 2014 at 12:36 PM, Sam Ravnborg wrote:
>> > On Wed, Jun 11, 2014 at 09:20:05AM -0700, Andy Lutomirski wrote:
>> >> This changes kbuild slightly because I didn't
On Wed, Jun 11, 2014 at 04:34:48AM -0400, Chen, Gong wrote:
> Implement a new debugfs interface for RAS susbsystem.
> A file named daemon_active is added there accordingly.
> This file is used to track if user space daemon enables
> perf/trace interface or not. One can track which daemon
> opens
On Wed, Jun 11, 2014 at 04:34:45AM -0400, Chen, Gong wrote:
> To avoid confuision and conflict of usage for RAS related trace event,
> add an unified RAS trace event stub.
>
> v5 -> v4: remove explicit RAS menuconfig.
> v4 -> v3: change dependency rule of RAS_TRACE.
> v3 -> v2: fix dependency in
On Wed, Jun 11, 2014 at 04:34:46AM -0400, Chen, Gong wrote:
> AER uses a separate trace interface by now. To make it
> consistent, move it into unified RAS trace interface.
>
> v3 -> v2: change dependency rule of RAS_TRACE.
> v2 -> v1: remove unnecessary dependency in drivers/ras/Kconfig.
>
>
On Thu, May 29, 2014 at 2:37 AM, Benjamin Gaignard
wrote:
> Compositor control all the input sub-device (VID, GDP)
> and the mixer(s).
> It is the main entry point for composition.
> Layer interface is used to control the abstracted layers.
>
> Add debug in mixer, GDP and VID
>
> Signed-off-by:
On Thu, 12 Jun 2014, Himangi Saraogi wrote:
> The various devm_ functions allocate memory that is released when a
> driver detaches. This patch uses devm_ioremap_resource for data
> that is allocated in the probe function of a platform device and
> is only freed in the remove function. The
unsigned value is never < 0
Cc: Konrad Rzeszutek Wilk
Cc: Boris Ostrovsky
Signed-off-by: Fabian Frederick
---
drivers/xen/events/events_base.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/xen/events/events_base.c b/drivers/xen/events/events_base.c
index
The deadlock logic is only required for futexes.
Remove the extra arguments for the public functions and also for the
futex specific ones which get always called with deadlock detection
enabled.
Signed-off-by: Thomas Gleixner
---
include/linux/rtmutex.h |6 +---
kernel/futex.c
On Wed, Jun 11, 2014 at 01:23:59PM -0400, Josh Boyer wrote:
> On Wed, Jun 11, 2014 at 12:20 PM, Andy Lutomirski wrote:
> > Rather than monkeying with barely-comprehensible static pattern
> > rules, just use an explicit loop.
> >
> > Signed-off-by: Andy Lutomirski
> > ---
> >
There is no point to keep the task ref across the check for lock
owner. Drop the ref before that, so the protection context is clear.
Found while documenting the chain walk.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c |5 +++--
1 file changed, 3 insertions(+), 2
Oleg noticed that rtmutex_slowtrylock() has a pointless check for
rt_mutex_owner(lock) != current.
To avoid calling try_to_take_rtmutex() we really want to check whether
the lock has an owner at all or whether the trylock failed because the
owner is NULL, but the RT_MUTEX_HAS_WAITERS bit is set.
unsigned value is never < 0
Cc: Dimitri Sivanich
Signed-off-by: Fabian Frederick
---
drivers/misc/sgi-gru/grukdump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/misc/sgi-gru/grukdump.c b/drivers/misc/sgi-gru/grukdump.c
index a3700a5..e0e0e7e 100644
---
The current implementation of try_to_take_rtmutex() is correct, but
requires more than a single brain twist to understand the clever
encoded conditionals.
Untangle it and document the cases proper.
Looks less efficient at the first glance, but actually reduces the
binary code size on x8664 by 80
Hi Willy,
On Mon, May 12, 2014 at 02:32:59AM +0200, Willy Tarreau wrote:
> 2.6.32-longterm review patch. If anyone has any objections, please let me
> know.
>
During Ubuntu Lucid kernel regression testing, after the merge of
2.6.32.62, we found problems with the following patches
[ 059/143]
The conditions under which deadlock detection is conducted are unclear
and undocumented.
Add constants instead of using 0/1 and provide a selection function
which hides the additional debug dependency from the calling code.
Add comments where needed.
Signed-off-by: Thomas Gleixner
Cc: Peter
Hopefully the last iteration of this.
I addressed all the review comments and added the following new ones:
1/n: plug unlock race.
Patch was separately posted already in the safety of
*mutex_unlock() thread.
2/n: Document and simplify the trylock path
3/n: Document and
Add a separate local variable for the boost/deboost logic to make the
code more readable. Add comments where appropriate.
Signed-off-by: Thomas Gleixner
---
kernel/locking/rtmutex.c | 58 ++-
1 file changed, 48 insertions(+), 10 deletions(-)
Index:
When the rtmutex fast path is enabled the slow unlock function can
create the following situation:
spin_lock(foo->m->wait_lock);
foo->m->owner = NULL;
rt_mutex_lock(foo->m); <-- fast path
free = atomic_dec_and_test(foo->refcnt);
In case the dead lock detector is enabled we follow the lock chain to
the end in rt_mutex_adjust_prio_chain, even if we could stop earlier
due to the priority/waiter constellation.
But once we are not longer the top priority waiter in a certain step
or the task holding the lock has already the
On Wed, Jun 11, 2014 at 12:31 PM, wrote:
> Hi Ulf,
> On 2014년 06월 11일 17:27, Ulf Hansson wrote:
>
>> On 11 June 2014 02:33, Jonghwa Lee wrote:
>>> When device uses generic pm domain, its own runtime suspend callback will be
>>> executed only when all devices in the same domain are suspended.
201 - 300 of 1520 matches
Mail list logo
