[PATCH v9 3/4] perf: xgene: Add APM X-Gene SoC Performance Monitoring Unit driver

This patch adds a driver for the SoC-wide (AKA uncore) PMU hardware found in APM X-Gene SoCs. Signed-off-by: Tai Nguyen Reviewed-by: Mark Rutland --- Documentation/perf/xgene-pmu.txt | 48 ++ drivers/perf/Kconfig |7 +

[PATCH v9 3/4] perf: xgene: Add APM X-Gene SoC Performance Monitoring Unit driver

This patch adds a driver for the SoC-wide (AKA uncore) PMU hardware found in APM X-Gene SoCs. Signed-off-by: Tai Nguyen Reviewed-by: Mark Rutland --- Documentation/perf/xgene-pmu.txt | 48 ++ drivers/perf/Kconfig |7 + drivers/perf/Makefile|1 +

[PATCH v9 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver

This patch adds the MAINTAINERS entry for APM X-Gene SoC PMU driver. Signed-off-by: Tai Nguyen --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 1209323..41938e7 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -841,6

[PATCH v9 1/4] MAINTAINERS: Add entry for APM X-Gene SoC PMU driver

This patch adds the MAINTAINERS entry for APM X-Gene SoC PMU driver. Signed-off-by: Tai Nguyen --- MAINTAINERS | 7 +++ 1 file changed, 7 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 1209323..41938e7 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -841,6 +841,13 @@ S: Supported

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 10:13 AM, Oleg Nesterov wrote: > On 07/14, John Stultz wrote: >> >> So I am seeing synchronize_sched called, and its taking the >> !rcu_gp_is_expedited path when I see the particularly bad latencies. >> >> I wonder if I just mucked up applying the patch? >

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 10:13 AM, Oleg Nesterov wrote: > On 07/14, John Stultz wrote: >> >> So I am seeing synchronize_sched called, and its taking the >> !rcu_gp_is_expedited path when I see the particularly bad latencies. >> >> I wonder if I just mucked up applying the patch? > > Probably

Re: [PATCH v8 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver

Hi Will, On Thu, Jul 14, 2016 at 6:16 AM, Will Deacon wrote: > On Mon, Jul 11, 2016 at 12:05:40PM -0700, Tai Nguyen wrote: >> In addition to the X-Gene ARM CPU performance monitoring unit (PMU), there >> are PMU for the SoC system devices such as L3 cache(s), I/O bridge(s),

Re: [PATCH v8 0/4] perf: Add APM X-Gene SoC Performance Monitoring Unit driver

Hi Will, On Thu, Jul 14, 2016 at 6:16 AM, Will Deacon wrote: > On Mon, Jul 11, 2016 at 12:05:40PM -0700, Tai Nguyen wrote: >> In addition to the X-Gene ARM CPU performance monitoring unit (PMU), there >> are PMU for the SoC system devices such as L3 cache(s), I/O bridge(s), >> memory controller

Re: [PATCH] Force processes to non-realtime before mm_exit

On Fri, Jun 03, 2016 at 04:18:44PM -0700, Brian Silverman wrote: > Without this, a realtime process which has called mlockall exiting > causes large latencies for other realtime processes at the same or > lower priorities. This seems like a fairly common use case too, because > realtime processes

Re: [PATCH] Force processes to non-realtime before mm_exit

On Fri, Jun 03, 2016 at 04:18:44PM -0700, Brian Silverman wrote: > Without this, a realtime process which has called mlockall exiting > causes large latencies for other realtime processes at the same or > lower priorities. This seems like a fairly common use case too, because > realtime processes

Re: [RT PATCH 2/2] timers: wakeup all timer waiters without holding the base lock

On Thu, 14 Jul 2016 19:19:47 +0200 Sebastian Andrzej Siewior wrote: > On 07/14/2016 06:09 PM, Steven Rostedt wrote: > > On Thu, 14 Jul 2016 18:05:04 +0200 > > Sebastian Andrzej Siewior wrote: > > > >> There should be no need to hold the base lock

Re: [RT PATCH 2/2] timers: wakeup all timer waiters without holding the base lock

On Thu, 14 Jul 2016 19:19:47 +0200 Sebastian Andrzej Siewior wrote: > On 07/14/2016 06:09 PM, Steven Rostedt wrote: > > On Thu, 14 Jul 2016 18:05:04 +0200 > > Sebastian Andrzej Siewior wrote: > > > >> There should be no need to hold the base lock during the wakeup. There > >> should be no

Re: [PATCH] drivers: gpu: drm: amd: powerplay: hwmgr: Remove unused variable

Hi list, I just wondered: I send the patch >14 days ago, 9 days ago it was reviewed by Rex Zhu. As far as I know, it isn't applied by now. At least I did not get a mail indicating that it was applied. Are there issues with the patch I missed? On 05-07-2016 15:06:59, Zhu, Rex wrote: > > Yes,

Re: [PATCH] drivers: gpu: drm: amd: powerplay: hwmgr: Remove unused variable

Hi list, I just wondered: I send the patch >14 days ago, 9 days ago it was reviewed by Rex Zhu. As far as I know, it isn't applied by now. At least I did not get a mail indicating that it was applied. Are there issues with the patch I missed? On 05-07-2016 15:06:59, Zhu, Rex wrote: > > Yes,

Re: [RT PATCH 2/2] timers: wakeup all timer waiters without holding the base lock

On 07/14/2016 06:09 PM, Steven Rostedt wrote: > On Thu, 14 Jul 2016 18:05:04 +0200 > Sebastian Andrzej Siewior wrote: > >> There should be no need to hold the base lock during the wakeup. There >> should be no boosting involved, the wakeup list has its own lock so it >>

Re: [RT PATCH 2/2] timers: wakeup all timer waiters without holding the base lock

On 07/14/2016 06:09 PM, Steven Rostedt wrote: > On Thu, 14 Jul 2016 18:05:04 +0200 > Sebastian Andrzej Siewior wrote: > >> There should be no need to hold the base lock during the wakeup. There >> should be no boosting involved, the wakeup list has its own lock so it >> should be safe to do this

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 06:45:47PM +0200, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 09:23:55AM -0700, Paul E. McKenney wrote: > > Hmmm... How does this handle the following sequence of events for > > the case where we are not biased towards the reader? > > > > o The per-CPU rwsem is set

Re: [PATCH v4] Force cppc_cpufreq to report values in KHz to fix user space reporting

On Thu, Jul 14, 2016 at 10:15:39AM -0600, Al Stone wrote: > On 07/14/2016 04:03 AM, Alexey Klimov wrote: > > Hi Al, > > > > On Tue, Jul 12, 2016 at 11:16:11AM -0600, Al Stone wrote: > >> When CPPC is being used by ACPI on arm64, user space tools such as > >> cpupower report CPU frequency values

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 06:45:47PM +0200, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 09:23:55AM -0700, Paul E. McKenney wrote: > > Hmmm... How does this handle the following sequence of events for > > the case where we are not biased towards the reader? > > > > o The per-CPU rwsem is set

Re: [PATCH v4] Force cppc_cpufreq to report values in KHz to fix user space reporting

On Thu, Jul 14, 2016 at 10:15:39AM -0600, Al Stone wrote: > On 07/14/2016 04:03 AM, Alexey Klimov wrote: > > Hi Al, > > > > On Tue, Jul 12, 2016 at 11:16:11AM -0600, Al Stone wrote: > >> When CPPC is being used by ACPI on arm64, user space tools such as > >> cpupower report CPU frequency values

Re: [PATCH 13/32] Documentation, x86: Documentation for Intel resource allocation user interface

On Thu, Jul 14, 2016 at 08:53:17AM +0200, Thomas Gleixner wrote: > > Happy to take suggestions for something in between those > > extremes :-) > > I'd suggest "resctrl" and the abbreviation dictionaries tell me that the most > common ones for resource are: R, RESORC, RES OK. "resctrl" it is. >

Re: [RT PATCH 1/2] timers: wakeup all timer waiters

On Thu, 14 Jul 2016 19:14:58 +0200 Sebastian Andrzej Siewior wrote: > On 07/14/2016 06:13 PM, Steven Rostedt wrote: > >> > >> -# define wakeup_timer_waiters(b) wake_up(&(b)->wait_for_running_timer) > >> +# define wakeup_timer_waiters(b) > >>

Re: [patch net-next 2/2] devlink: fix trace format string

On Thu, 14 Jul 2016 10:07:38 -0700 Randy Dunlap wrote: > On 07/14/16 02:37, Jiri Pirko wrote: > > From: Arnd Bergmann > > > > Including devlink.h on ARM and probably other 32-bit architectures results > > in > > a harmless warning: > > > > In file

Re: [PATCH 13/32] Documentation, x86: Documentation for Intel resource allocation user interface

On Thu, Jul 14, 2016 at 08:53:17AM +0200, Thomas Gleixner wrote: > > Happy to take suggestions for something in between those > > extremes :-) > > I'd suggest "resctrl" and the abbreviation dictionaries tell me that the most > common ones for resource are: R, RESORC, RES OK. "resctrl" it is. >

Re: [RT PATCH 1/2] timers: wakeup all timer waiters

On Thu, 14 Jul 2016 19:14:58 +0200 Sebastian Andrzej Siewior wrote: > On 07/14/2016 06:13 PM, Steven Rostedt wrote: > >> > >> -# define wakeup_timer_waiters(b) wake_up(&(b)->wait_for_running_timer) > >> +# define wakeup_timer_waiters(b) > >> wake_up_all(&(b)->wait_for_running_timer) > >

Re: [patch net-next 2/2] devlink: fix trace format string

On Thu, 14 Jul 2016 10:07:38 -0700 Randy Dunlap wrote: > On 07/14/16 02:37, Jiri Pirko wrote: > > From: Arnd Bergmann > > > > Including devlink.h on ARM and probably other 32-bit architectures results > > in > > a harmless warning: > > > > In file included from

[ANNOUNCE] 4.6.4-rt7

Dear RT folks! I'm pleased to announce the v4.6.4-rt7 patch set. Changes since v4.6.4-rt6: - Wake up all waiters of del_timer_sync(). Usually there should not be more than just one waiter (per timer base) but it possible to gain more. - Wake up the waiters of del_timer_sync() after

[ANNOUNCE] 4.6.4-rt7

Dear RT folks! I'm pleased to announce the v4.6.4-rt7 patch set. Changes since v4.6.4-rt6: - Wake up all waiters of del_timer_sync(). Usually there should not be more than just one waiter (per timer base) but it possible to gain more. - Wake up the waiters of del_timer_sync() after

Re: [RT PATCH 1/2] timers: wakeup all timer waiters

On 07/14/2016 06:13 PM, Steven Rostedt wrote: >> >> -# define wakeup_timer_waiters(b)wake_up(&(b)->wait_for_running_timer) >> +# define wakeup_timer_waiters(b) >> wake_up_all(&(b)->wait_for_running_timer) > > OK, I just received this patch (way after patch 2) > > I'm assuming that

Re: [RT PATCH 1/2] timers: wakeup all timer waiters

On 07/14/2016 06:13 PM, Steven Rostedt wrote: >> >> -# define wakeup_timer_waiters(b)wake_up(&(b)->wait_for_running_timer) >> +# define wakeup_timer_waiters(b) >> wake_up_all(&(b)->wait_for_running_timer) > > OK, I just received this patch (way after patch 2) > > I'm assuming that

Re: [PATCH v2 1/7] lib/dlock-list: Distributed and lock-protected lists

On 07/14/2016 07:50 AM, Tejun Heo wrote: Hello, On Wed, Jul 13, 2016 at 10:54:19PM -0400, Waiman Long wrote: On 07/13/2016 12:08 PM, Tejun Heo wrote: On Mon, Jul 11, 2016 at 01:32:06PM -0400, Waiman Long wrote: ... A new header file include/linux/dlock-list.h will be added with the Heh, I

Re: [PATCH v2 1/7] lib/dlock-list: Distributed and lock-protected lists

On 07/14/2016 07:50 AM, Tejun Heo wrote: Hello, On Wed, Jul 13, 2016 at 10:54:19PM -0400, Waiman Long wrote: On 07/13/2016 12:08 PM, Tejun Heo wrote: On Mon, Jul 11, 2016 at 01:32:06PM -0400, Waiman Long wrote: ... A new header file include/linux/dlock-list.h will be added with the Heh, I

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On 07/14, John Stultz wrote: > > So I am seeing synchronize_sched called, and its taking the > !rcu_gp_is_expedited path when I see the particularly bad latencies. > > I wonder if I just mucked up applying the patch? Probably yes... Just in case, could you try the patch below? Of course, without

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On 07/14, John Stultz wrote: > > So I am seeing synchronize_sched called, and its taking the > !rcu_gp_is_expedited path when I see the particularly bad latencies. > > I wonder if I just mucked up applying the patch? Probably yes... Just in case, could you try the patch below? Of course, without

Re: [patch net-next 1/2] tracing: change owner name to driver name for devlink hwmsg tracepoint

On Thu, 14 Jul 2016 10:07:33 -0700 Randy Dunlap wrote: > On 07/14/16 02:37, Jiri Pirko wrote: > > From: Jiri Pirko > > > > Turned on that driver->owner which is struct module is not available when > > modules are disabled. Better to depend on a driver

Re: [patch net-next 1/2] tracing: change owner name to driver name for devlink hwmsg tracepoint

On Thu, 14 Jul 2016 10:07:33 -0700 Randy Dunlap wrote: > On 07/14/16 02:37, Jiri Pirko wrote: > > From: Jiri Pirko > > > > Turned on that driver->owner which is struct module is not available when > > modules are disabled. Better to depend on a driver name which is > > always available. > > >

[PATCH] metag: Remove duplicate KERN_ prefix

Use a bare printk to avoid a duplicate KERN_ in logging output. Signed-off-by: Joe Perches --- arch/metag/mm/fault.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/metag/mm/fault.c b/arch/metag/mm/fault.c index 372783a..c765b36 100644 ---

[PATCH] metag: Remove duplicate KERN_ prefix

Use a bare printk to avoid a duplicate KERN_ in logging output. Signed-off-by: Joe Perches --- arch/metag/mm/fault.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/metag/mm/fault.c b/arch/metag/mm/fault.c index 372783a..c765b36 100644 --- a/arch/metag/mm/fault.c +++

Re: [PATCH v15 00/10] arm64: Add kernel probes (kprobes) support

On 07/14/2016 12:22 PM, Catalin Marinas wrote: > On Fri, Jul 08, 2016 at 12:35:44PM -0400, David Long wrote: >> David A. Long (3): >> arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature >> arm64: Add more test functions to insn.c >> arm64: add conditional instruction simulation support >> >>

Re: [PATCH v15 00/10] arm64: Add kernel probes (kprobes) support

On 07/14/2016 12:22 PM, Catalin Marinas wrote: > On Fri, Jul 08, 2016 at 12:35:44PM -0400, David Long wrote: >> David A. Long (3): >> arm64: Add HAVE_REGS_AND_STACK_ACCESS_API feature >> arm64: Add more test functions to insn.c >> arm64: add conditional instruction simulation support >> >>

Re: System freezes after OOM

On 07/14/2016 05:31 PM, Michal Hocko wrote: On Thu 14-07-16 16:08:28, Ondrej Kozina wrote: [...] As Mikulas pointed out, this doesn't work. The system froze as well with the patch above. Will try to tweak the patch with Mikulas's suggestion... Thank you for testing! Do you happen to have

Re: System freezes after OOM

On 07/14/2016 05:31 PM, Michal Hocko wrote: On Thu 14-07-16 16:08:28, Ondrej Kozina wrote: [...] As Mikulas pointed out, this doesn't work. The system froze as well with the patch above. Will try to tweak the patch with Mikulas's suggestion... Thank you for testing! Do you happen to have

Re: [patch net-next 2/2] devlink: fix trace format string

On 07/14/16 02:37, Jiri Pirko wrote: > From: Arnd Bergmann > > Including devlink.h on ARM and probably other 32-bit architectures results in > a harmless warning: > > In file included from ../include/trace/define_trace.h:95:0, > from

Re: [patch net-next 2/2] devlink: fix trace format string

On 07/14/16 02:37, Jiri Pirko wrote: > From: Arnd Bergmann > > Including devlink.h on ARM and probably other 32-bit architectures results in > a harmless warning: > > In file included from ../include/trace/define_trace.h:95:0, > from ../include/trace/events/devlink.h:51, >

Re: [patch net-next 1/2] tracing: change owner name to driver name for devlink hwmsg tracepoint

On 07/14/16 02:37, Jiri Pirko wrote: > From: Jiri Pirko > > Turned on that driver->owner which is struct module is not available when > modules are disabled. Better to depend on a driver name which is > always available. > > Reported-by: Randy Dunlap >

Re: [patch net-next 1/2] tracing: change owner name to driver name for devlink hwmsg tracepoint

On 07/14/16 02:37, Jiri Pirko wrote: > From: Jiri Pirko > > Turned on that driver->owner which is struct module is not available when > modules are disabled. Better to depend on a driver name which is > always available. > > Reported-by: Randy Dunlap > Fixes: e5224f0fe2 ("devlink: add hardware

[PATCH] staging: octeon: Use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Signed-off-by: Javier Martinez Canillas --- drivers/staging/octeon/ethernet.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] staging: octeon: Use IS_ENABLED() instead of checking for built-in or module

The IS_ENABLED() macro checks if a Kconfig symbol has been enabled either built-in or as a module, use that macro instead of open coding the same. Signed-off-by: Javier Martinez Canillas --- drivers/staging/octeon/ethernet.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On 07/14, Peter Zijlstra wrote: > > On Thu, Jul 14, 2016 at 04:58:44PM +0200, Oleg Nesterov wrote: > > > > But note that we do not need RCU_NONE. All we need is the trivial change > > below. > > Hurm, maybe. So having that unbalanced keeps us in GP_PASSED state and > since we'll never drop

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On 07/14, Peter Zijlstra wrote: > > On Thu, Jul 14, 2016 at 04:58:44PM +0200, Oleg Nesterov wrote: > > > > But note that we do not need RCU_NONE. All we need is the trivial change > > below. > > Hurm, maybe. So having that unbalanced keeps us in GP_PASSED state and > since we'll never drop

[PATCH v1] x86, kasan, ftrace: Put APIC interrupt handlers into .irqentry.text

When building with CONFIG_FUNCTION_GRAPH_TRACER or CONFIG_KASAN, put the APIC interrupt handlers into the .irqentry.text section. This is needed because both KASAN and function graph tracer use __irqentry_text_start and __irqentry_text_end to determine whether a function is an IRQ entry point.

[PATCH v1] x86, kasan, ftrace: Put APIC interrupt handlers into .irqentry.text

When building with CONFIG_FUNCTION_GRAPH_TRACER or CONFIG_KASAN, put the APIC interrupt handlers into the .irqentry.text section. This is needed because both KASAN and function graph tracer use __irqentry_text_start and __irqentry_text_end to determine whether a function is an IRQ entry point.

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 9:49 AM, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 09:43:40AM -0700, John Stultz wrote: >> On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: >> > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: >> >>

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 9:49 AM, Peter Zijlstra wrote: > On Thu, Jul 14, 2016 at 09:43:40AM -0700, John Stultz wrote: >> On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: >> > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: >> >> So, IIRC, the trade-off is a full memory

Re: [PATCH] Coccinelle: Script to use roundup and DIV_ROUND_UP

On Thu, 14 Jul 2016, Amitoj Kaur Chawla wrote: > This script replaces manual calculations by using the predefined > macros in kernel.h, DIV_ROUND_UP and roundup for readability purposes. > > Signed-off-by: Amitoj Kaur Chawla Acked-by: Julia Lawall

Re: [PATCH] Coccinelle: Script to use roundup and DIV_ROUND_UP

On Thu, 14 Jul 2016, Amitoj Kaur Chawla wrote: > This script replaces manual calculations by using the predefined > macros in kernel.h, DIV_ROUND_UP and roundup for readability purposes. > > Signed-off-by: Amitoj Kaur Chawla Acked-by: Julia Lawall > --- >

[PATCH] ARM: tegra: fix erroneous address in dts

c90bb7b enabled the high speed UARTs of the Jetson TK1. The address specification inside the dts is wrong. Fix it and use the correct address. Fixes: c90bb7b9b9 ("ARM: tegra: Add high speed UARTs to Jetson TK1 device tree") Signed-off-by: Ralf Ramsauer ---

[PATCH] ARM: tegra: fix erroneous address in dts

c90bb7b enabled the high speed UARTs of the Jetson TK1. The address specification inside the dts is wrong. Fix it and use the correct address. Fixes: c90bb7b9b9 ("ARM: tegra: Add high speed UARTs to Jetson TK1 device tree") Signed-off-by: Ralf Ramsauer ---

Re: [PATCH] KVM: release anon file in failure path of vm creation

On 14/07/2016 18:46, Al Viro wrote: > On Tue, Jul 12, 2016 at 12:24:39PM +0200, Paolo Bonzini wrote: > >> On 12/07/2016 11:38, Liu Shuo wrote: >>> The failure of create debugfs of VM will return directly without release >>> the anon file. It will leak memory and file descriptors, even through

Re: [PATCH] KVM: release anon file in failure path of vm creation

On 14/07/2016 18:46, Al Viro wrote: > On Tue, Jul 12, 2016 at 12:24:39PM +0200, Paolo Bonzini wrote: > >> On 12/07/2016 11:38, Liu Shuo wrote: >>> The failure of create debugfs of VM will return directly without release >>> the anon file. It will leak memory and file descriptors, even through

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Wed, Jul 13, 2016 at 4:02 PM, Paul E. McKenney wrote: > On Wed, Jul 13, 2016 at 03:39:37PM -0700, John Stultz wrote: >> >> But otherwise both patches look great and are working well! >> >> Do you mind marking them both for stable 4.4+? > > OK, looks like it does

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Wed, Jul 13, 2016 at 4:02 PM, Paul E. McKenney wrote: > On Wed, Jul 13, 2016 at 03:39:37PM -0700, John Stultz wrote: >> >> But otherwise both patches look great and are working well! >> >> Do you mind marking them both for stable 4.4+? > > OK, looks like it does qualify in the "fix a notable

Re: [PATCH v5 14/32] x86/mm/64: Enable vmapped stacks

On Thu, Jul 14, 2016 at 1:34 AM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> On Wed, Jul 13, 2016 at 12:53 AM, Ingo Molnar wrote: >> > >> > * Andy Lutomirski wrote: >> > >> >> This allows x86_64 kernels to

Re: [PATCH v5 14/32] x86/mm/64: Enable vmapped stacks

On Thu, Jul 14, 2016 at 1:34 AM, Ingo Molnar wrote: > > * Andy Lutomirski wrote: > >> On Wed, Jul 13, 2016 at 12:53 AM, Ingo Molnar wrote: >> > >> > * Andy Lutomirski wrote: >> > >> >> This allows x86_64 kernels to enable vmapped stacks. There are a >> >> couple of interesting bits. >> > >>

Re: linux-next: Tree for Jul 14 (overlayfs)

On 07/13/16 23:18, Stephen Rothwell wrote: > Hi all, > > Changes since 20160713: > on i386, when: # CONFIG_FS_POSIX_ACL is not set fs/built-in.o: In function `ovl_posix_acl_xattr_set': super.c:(.text+0x44223): undefined reference to `posix_acl_from_xattr' -- ~Randy

Re: linux-next: Tree for Jul 14 (overlayfs)

On 07/13/16 23:18, Stephen Rothwell wrote: > Hi all, > > Changes since 20160713: > on i386, when: # CONFIG_FS_POSIX_ACL is not set fs/built-in.o: In function `ovl_posix_acl_xattr_set': super.c:(.text+0x44223): undefined reference to `posix_acl_from_xattr' -- ~Randy

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 09:43:40AM -0700, John Stultz wrote: > On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: > > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: > >> So, IIRC, the trade-off is a full memory barrier in read_lock and > >> read_unlock()

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 09:43:40AM -0700, John Stultz wrote: > On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: > > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: > >> So, IIRC, the trade-off is a full memory barrier in read_lock and > >> read_unlock() vs sync_sched() in

[PATCH] Coccinelle: Script to use roundup and DIV_ROUND_UP

This script replaces manual calculations by using the predefined macros in kernel.h, DIV_ROUND_UP and roundup for readability purposes. Signed-off-by: Amitoj Kaur Chawla --- scripts/coccinelle/api/roundup.cocci | 215 +++ 1 file changed, 215

[PATCH] Coccinelle: Script to use roundup and DIV_ROUND_UP

This script replaces manual calculations by using the predefined macros in kernel.h, DIV_ROUND_UP and roundup for readability purposes. Signed-off-by: Amitoj Kaur Chawla --- scripts/coccinelle/api/roundup.cocci | 215 +++ 1 file changed, 215 insertions(+) create

Re: [PATCH] KVM: release anon file in failure path of vm creation

On Tue, Jul 12, 2016 at 12:24:39PM +0200, Paolo Bonzini wrote: > On 12/07/2016 11:38, Liu Shuo wrote: > > The failure of create debugfs of VM will return directly without release > > the anon file. It will leak memory and file descriptors, even through > > be not serious. > > > > Signed-off-by:

Re: [PATCH] KVM: release anon file in failure path of vm creation

On Tue, Jul 12, 2016 at 12:24:39PM +0200, Paolo Bonzini wrote: > On 12/07/2016 11:38, Liu Shuo wrote: > > The failure of create debugfs of VM will return directly without release > > the anon file. It will leak memory and file descriptors, even through > > be not serious. > > > > Signed-off-by:

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 09:23:55AM -0700, Paul E. McKenney wrote: > Hmmm... How does this handle the following sequence of events for > the case where we are not biased towards the reader? > > o The per-CPU rwsem is set up with RCU_NONE and readers_slow > (as opposed to readers_block).

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 09:23:55AM -0700, Paul E. McKenney wrote: > Hmmm... How does this handle the following sequence of events for > the case where we are not biased towards the reader? > > o The per-CPU rwsem is set up with RCU_NONE and readers_slow > (as opposed to readers_block).

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: >> So, IIRC, the trade-off is a full memory barrier in read_lock and >> read_unlock() vs sync_sched() in write. >> >> Full memory barriers are expensive

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 6:18 AM, Peter Zijlstra wrote: > On Wed, Jul 13, 2016 at 10:51:02PM +0200, Peter Zijlstra wrote: >> So, IIRC, the trade-off is a full memory barrier in read_lock and >> read_unlock() vs sync_sched() in write. >> >> Full memory barriers are expensive and while the combined

[PATCH v4 1/4] dmi: remove const from return of dmi_find_device

From: Corey Minyard A fwnode_handle is being added to dmi_device, and that will need to be updated. So remove the const. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski

[PATCH v4 1/4] dmi: remove const from return of dmi_find_device

From: Corey Minyard A fwnode_handle is being added to dmi_device, and that will need to be updated. So remove the const. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski --- drivers/firmware/dmi_scan.c | 11 +-- include/linux/dmi.h

[PATCH 04/10] Documentation: dt: socfpga: Add Arria10 QSPI EDAC binding

From: Thor Thayer Add the device tree bindings needed to support the Altera QSPI FIFO buffer EDAC on the Arria10 chip. Signed-off-by: Thor Thayer --- .../bindings/arm/altera/socfpga-eccmgr.txt | 16 1

[PATCH 04/10] Documentation: dt: socfpga: Add Arria10 QSPI EDAC binding

From: Thor Thayer Add the device tree bindings needed to support the Altera QSPI FIFO buffer EDAC on the Arria10 chip. Signed-off-by: Thor Thayer --- .../bindings/arm/altera/socfpga-eccmgr.txt | 16 1 file changed, 16 insertions(+) diff --git

Re: [PATCH v2 11/13] sched/fair: Avoid pulling tasks from non-overloaded higher capacity groups

On 06/30/2016 12:49 AM, Morten Rasmussen wrote: > On Thu, Jun 23, 2016 at 02:20:48PM -0700, Sai Gurrappadi wrote: >> Hi Morten, >> >> On 06/22/2016 10:03 AM, Morten Rasmussen wrote: >> >> [...] >> >>> >>> +/* >>> + * group_smaller_cpu_capacity: Returns true if sched_group sg has smaller >>> + *

Re: [PATCH v2 11/13] sched/fair: Avoid pulling tasks from non-overloaded higher capacity groups

On 06/30/2016 12:49 AM, Morten Rasmussen wrote: > On Thu, Jun 23, 2016 at 02:20:48PM -0700, Sai Gurrappadi wrote: >> Hi Morten, >> >> On 06/22/2016 10:03 AM, Morten Rasmussen wrote: >> >> [...] >> >>> >>> +/* >>> + * group_smaller_cpu_capacity: Returns true if sched_group sg has smaller >>> + *

Re: [PATCH 0/2] ipc/sem.c: sem_lock fixes

Hi Andrew, On 07/14/2016 12:05 AM, Andrew Morton wrote: On Wed, 13 Jul 2016 07:06:50 +0200 Manfred Spraul wrote: Hi Andrew, Hi Peter, next version of the sem_lock() fixes: The patches are again vs. tip. Patch 1 is ready for merging, Patch 2 is for review. -

Re: [PATCH 0/2] ipc/sem.c: sem_lock fixes

Hi Andrew, On 07/14/2016 12:05 AM, Andrew Morton wrote: On Wed, 13 Jul 2016 07:06:50 +0200 Manfred Spraul wrote: Hi Andrew, Hi Peter, next version of the sem_lock() fixes: The patches are again vs. tip. Patch 1 is ready for merging, Patch 2 is for review. - Patch 1 is the patch as in

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 04:58:44PM +0200, Oleg Nesterov wrote: > > But note that we do not need RCU_NONE. All we need is the trivial change > below. Hurm, maybe. So having that unbalanced keeps us in GP_PASSED state and since we'll never drop gp_count back to 0 nothing will ever happen. Cute,

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 04:58:44PM +0200, Oleg Nesterov wrote: > > But note that we do not need RCU_NONE. All we need is the trivial change > below. Hurm, maybe. So having that unbalanced keeps us in GP_PASSED state and since we'll never drop gp_count back to 0 nothing will ever happen. Cute,

[PATCH v4 3/4] dmi: Add IPMI DMI scanning to the DMI code

From: Corey Minyard It makes more sense to be there, and it's cleaner with the upcoming conversion of IPMI DMI to a platform device. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy

[PATCH v4 3/4] dmi: Add IPMI DMI scanning to the DMI code

From: Corey Minyard It makes more sense to be there, and it's cleaner with the upcoming conversion of IPMI DMI to a platform device. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski --- drivers/firmware/dmi_scan.c | 108

[PATCH v4 0/4] dmi: Rework to get IPMI autoloading from DMI tables

No changes at all, just rebasing on current kernel.org and hoping it gets approved and/or put into a subsystem tree. -corey

[PATCH v4 4/4] dmi: Add IPMI DMI devices as platform devices

From: Corey Minyard Have DMI create a platform device for every IPMI device it finds. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski ---

[PATCH v4 0/4] dmi: Rework to get IPMI autoloading from DMI tables

No changes at all, just rebasing on current kernel.org and hoping it gets approved and/or put into a subsystem tree. -corey

[PATCH v4 4/4] dmi: Add IPMI DMI devices as platform devices

From: Corey Minyard Have DMI create a platform device for every IPMI device it finds. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski --- drivers/firmware/dmi_scan.c | 55 +++-- 1 file changed, 53

[PATCH v4 2/4] dmi: Add a DMI firmware node and handling

From: Corey Minyard This is so that an IPMI platform device can be created from a DMI firmware entry. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski

[PATCH v4 2/4] dmi: Add a DMI firmware node and handling

From: Corey Minyard This is so that an IPMI platform device can be created from a DMI firmware entry. Signed-off-by: Corey Minyard Cc: Jean Delvare Cc: Andy Lutomirski Tested-by: Andy Lutomirski --- drivers/firmware/dmi_scan.c | 16 ++-- include/linux/dmi.h | 14

Applied "regulator: act8865: Fix missing of_node_put() in act8865_pdata_from_dt()" to the regulator tree

The patch regulator: act8865: Fix missing of_node_put() in act8865_pdata_from_dt() has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "ASoC: mediatek: mt2701: fix non static symbol warning" to the asoc tree

The patch ASoC: mediatek: mt2701: fix non static symbol warning has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Applied "regulator: act8865: Fix missing of_node_put() in act8865_pdata_from_dt()" to the regulator tree

The patch regulator: act8865: Fix missing of_node_put() in act8865_pdata_from_dt() has been applied to the regulator tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git All being well this means that it will be integrated into the linux-next tree (usually

Applied "ASoC: mediatek: mt2701: fix non static symbol warning" to the asoc tree

The patch ASoC: mediatek: mt2701: fix non static symbol warning has been applied to the asoc tree at git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 11:07:15AM -0400, Tejun Heo wrote: > How? While write lock is pending, no new reader is allowed. Look at the new percpu_down_write (the old one is similar in concept): + void percpu_down_write(struct percpu_rw_semaphore *sem) + { + down_write(>rw_sem); + +

Re: Severe performance regression w/ 4.4+ on Android due to cgroup locking changes

On Thu, Jul 14, 2016 at 11:07:15AM -0400, Tejun Heo wrote: > How? While write lock is pending, no new reader is allowed. Look at the new percpu_down_write (the old one is similar in concept): + void percpu_down_write(struct percpu_rw_semaphore *sem) + { + down_write(>rw_sem); + +

<    3   4   5   6   7   8   9   10   11   12   >