Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!

On Mon, Feb 15, 2016 at 4:50 AM, Sudip Mukherjee wrote: > On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote: >> Greetings, >> >> 0day kernel testing robot got the below dmesg and the first bad commit is >> >>

Re: [ppdev] e7223f1860: kernel BUG at drivers/base/driver.c:153!

On Mon, Feb 15, 2016 at 4:50 AM, Sudip Mukherjee wrote: > On Mon, Feb 15, 2016 at 04:20:45PM +0800, kernel test robot wrote: >> Greetings, >> >> 0day kernel testing robot got the below dmesg and the first bad commit is >> >> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git >>

Re: [PATCH v10 7/9] arm64: Add trampoline code for kretprobes

On 03/01/2016 01:19 PM, Marc Zyngier wrote: > On 01/03/16 02:57, David Long wrote: >> From: William Cohen >> >> The trampoline code is used by kretprobes to capture a return from a probed >> function. This is done by saving the registers, calling the handler, and >> restoring

Re: [PATCH v10 7/9] arm64: Add trampoline code for kretprobes

On 03/01/2016 01:19 PM, Marc Zyngier wrote: > On 01/03/16 02:57, David Long wrote: >> From: William Cohen >> >> The trampoline code is used by kretprobes to capture a return from a probed >> function. This is done by saving the registers, calling the handler, and >> restoring the registers. The

Re: [PATCH] objtool: Disable stack validation when CROSS_COMPILE is used

On Wed, Mar 02, 2016 at 01:27:35PM +1100, Stephen Rothwell wrote: > Hi Josh, > > On Tue, 1 Mar 2016 15:54:51 -0600 Josh Poimboeuf wrote: > > > > Changing it to use the host compiler would probably be an easy fix, but > > that would expose a harder bug related to endianness.

Re: [PATCH] objtool: Disable stack validation when CROSS_COMPILE is used

On Wed, Mar 02, 2016 at 01:27:35PM +1100, Stephen Rothwell wrote: > Hi Josh, > > On Tue, 1 Mar 2016 15:54:51 -0600 Josh Poimboeuf wrote: > > > > Changing it to use the host compiler would probably be an easy fix, but > > that would expose a harder bug related to endianness. > > Just by luck, my

Re: [PATCH 1/5] usb: gadget: f_midi: refactor state machine

Felipe F. Tonello wrote: > This refactor results in a cleaner state machine code It increases the number of states, and now juggles two state variables. I cannot agree to it being cleaner. > and as a result fixed a bug when packaging a USB-MIDI packet right after > a non-conformant MIDI byte

Re: [PATCH 1/5] usb: gadget: f_midi: refactor state machine

Felipe F. Tonello wrote: > This refactor results in a cleaner state machine code It increases the number of states, and now juggles two state variables. I cannot agree to it being cleaner. > and as a result fixed a bug when packaging a USB-MIDI packet right after > a non-conformant MIDI byte

Re: [PATCH v2] locktorture: Fix NULL pointer when torture_type is invalid

On Wed, Mar 02, 2016 at 11:55:43AM -0800, Davidlohr Bueso wrote: > On Tue, 02 Feb 2016, Davidlohr Bueso wrote: > > I've just hit this issue myself and remembered this thread :) > > Paul, folks, does the below patch look reasonable to you? If so > I can properly resend. thanks. If it works for

Re: [PATCH v2] locktorture: Fix NULL pointer when torture_type is invalid

On Wed, Mar 02, 2016 at 11:55:43AM -0800, Davidlohr Bueso wrote: > On Tue, 02 Feb 2016, Davidlohr Bueso wrote: > > I've just hit this issue myself and remembered this thread :) > > Paul, folks, does the below patch look reasonable to you? If so > I can properly resend. thanks. If it works for

Re: [GIT PULL] at91: dt for 4.6 #2

Hi, On 02/03/2016 at 21:50:59 +0100, Arnd Bergmann wrote : > I see that your gpg key has expired last week, you may want to do something > about that, I think you can just update the date rather than creating a > new key. > You probably want to pull his key, it was updated today. --

Re: [GIT PULL] at91: dt for 4.6 #2

Hi, On 02/03/2016 at 21:50:59 +0100, Arnd Bergmann wrote : > I see that your gpg key has expired last week, you may want to do something > about that, I think you can just update the date rather than creating a > new key. > You probably want to pull his key, it was updated today. --

Re: [REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2

On 3/2/16 12:31 PM, Jeremiah Mahler wrote: On Tue, Mar 01, 2016 at 08:11:54AM +, Dexuan Cui wrote: Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V guest, even when I didn't configure any NIC for the guest: [ 72.604249] unregister_netdevice: waiting for lo to

Re: [REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2

On 3/2/16 12:31 PM, Jeremiah Mahler wrote: On Tue, Mar 01, 2016 at 08:11:54AM +, Dexuan Cui wrote: Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V guest, even when I didn't configure any NIC for the guest: [ 72.604249] unregister_netdevice: waiting for lo to

Re: Question about prio_changed_dl()

On Wed, Mar 02, 2016 at 09:16:57PM +0100, luca abeni wrote: > > That code no longer exists like that. > Uh... I must have done something wrong, then (I was convinced I pulled > from master and rebased my patch before testing and sending it, but > probably something went wrong). > Sorry about that.

Re: Question about prio_changed_dl()

On Wed, Mar 02, 2016 at 09:16:57PM +0100, luca abeni wrote: > > That code no longer exists like that. > Uh... I must have done something wrong, then (I was convinced I pulled > from master and rebased my patch before testing and sending it, but > probably something went wrong). > Sorry about that.

Re: [PATCH v10 07/12] task_isolation: add debug boot flag

On 3/2/2016 3:37 PM, Peter Zijlstra wrote: On Wed, Mar 02, 2016 at 03:09:31PM -0500, Chris Metcalf wrote: +void task_isolation_debug(int cpu) +{ + struct task_struct *p; + + if (!task_isolation_possible(cpu)) + return; + + rcu_read_lock(); + p =

Re: [PATCH v10 07/12] task_isolation: add debug boot flag

On 3/2/2016 3:37 PM, Peter Zijlstra wrote: On Wed, Mar 02, 2016 at 03:09:31PM -0500, Chris Metcalf wrote: +void task_isolation_debug(int cpu) +{ + struct task_struct *p; + + if (!task_isolation_possible(cpu)) + return; + + rcu_read_lock(); + p =

Re: [GIT PULL] at91: dt for 4.6 #2

On Wednesday 02 March 2016 17:05:22 Nicolas Ferre wrote: > A second batch of DT updates for 4.6. This time it is based on 4.5-rc3 as one > of the patches fixes an node that was changed during 4.5-rc phase. As I saw > that your "next/dt" branches are based on 4.5-rc3, I thought it wouldn't be a >

Re: [GIT PULL] at91: dt for 4.6 #2

On Wednesday 02 March 2016 17:05:22 Nicolas Ferre wrote: > A second batch of DT updates for 4.6. This time it is based on 4.5-rc3 as one > of the patches fixes an node that was changed during 4.5-rc phase. As I saw > that your "next/dt" branches are based on 4.5-rc3, I thought it wouldn't be a >

[PATCH RT 1/7] latencyhist: disable jump-labels

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Atleast on X86 we die a recursive death |CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198 |Hardware name: QEMU Standard PC

[PATCH RT 1/7] latencyhist: disable jump-labels

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior Atleast on X86 we die a recursive death |CPU: 3 PID: 585 Comm: bash Not tainted 4.4.1-rt4+ #198 |Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS

Re: [PATCH v14] x86, mce: Add memcpy_mcsafe()

On Thu, Feb 18, 2016 at 11:47:26AM -0800, Tony Luck wrote: > Make use of the EXTABLE_FAULT exception table entries to write > a kernel copy routine that doesn't crash the system if it > encounters a machine check. Prime use case for this is to copy > from large arrays of non-volatile memory used

Re: [PATCH v14] x86, mce: Add memcpy_mcsafe()

On Thu, Feb 18, 2016 at 11:47:26AM -0800, Tony Luck wrote: > Make use of the EXTABLE_FAULT exception table entries to write > a kernel copy routine that doesn't crash the system if it > encounters a machine check. Prime use case for this is to copy > from large arrays of non-volatile memory used

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On Wed, Mar 02, 2016 at 08:50:53PM +0100, Borislav Petkov wrote: > But better safe than sorry. I got this, it looks good when I'm single-stepping through it with gdb and it boots fine in kvm. I'll run it on baremetal tomorrow: /* * Setup stack for verify_cpu(): make sure we

Re: [RFC PATCH] x86: Make sure verify_cpu has a good stack

On Wed, Mar 02, 2016 at 08:50:53PM +0100, Borislav Petkov wrote: > But better safe than sorry. I got this, it looks good when I'm single-stepping through it with gdb and it boots fine in kvm. I'll run it on baremetal tomorrow: /* * Setup stack for verify_cpu(): make sure we

Re: [PATCH v5 22/22] sound/usb: Use Media Controller API to share media resources

On Wed, Mar 02, 2016 at 09:50:31AM -0700, Shuah Khan wrote: > + mctl = kzalloc(sizeof(*mctl), GFP_KERNEL); > + if (!mctl) > + return -ENOMEM; > + > + mctl->media_dev = mdev; > + if (stream == SNDRV_PCM_STREAM_PLAYBACK) { > + intf_type =

Re: [PATCH v5 22/22] sound/usb: Use Media Controller API to share media resources

On Wed, Mar 02, 2016 at 09:50:31AM -0700, Shuah Khan wrote: > + mctl = kzalloc(sizeof(*mctl), GFP_KERNEL); > + if (!mctl) > + return -ENOMEM; > + > + mctl->media_dev = mdev; > + if (stream == SNDRV_PCM_STREAM_PLAYBACK) { > + intf_type =

[PATCH v2] sparc64: Add support for Application Data Integrity (ADI)

Enable Application Data Integrity (ADI) support in the sparc kernel for applications to use ADI in userspace. ADI is a new feature supported on sparc M7 and newer processors. ADI is supported for data fetches only and not instruction fetches. This patch adds prctl commands to enable and disable

[PATCH v2] sparc64: Add support for Application Data Integrity (ADI)

Enable Application Data Integrity (ADI) support in the sparc kernel for applications to use ADI in userspace. ADI is a new feature supported on sparc M7 and newer processors. ADI is supported for data fetches only and not instruction fetches. This patch adds prctl commands to enable and disable

[PATCH] MAINTAINERS: update arch/tile maintainer email domain

Mellanox has acquired EZchip, so my email address as arch/tile maintainer will now change to cmetc...@mellanox.com. http://www.mellanox.com/page/press_release_item?id=1681 Signed-off-by: Chris Metcalf --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH] MAINTAINERS: update arch/tile maintainer email domain

Mellanox has acquired EZchip, so my email address as arch/tile maintainer will now change to cmetc...@mellanox.com. http://www.mellanox.com/page/press_release_item?id=1681 Signed-off-by: Chris Metcalf --- MAINTAINERS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH] sparc64: Add support for Application Data Integrity (ADI)

On 03/02/2016 01:26 PM, kbuild test robot wrote: Hi Khalid, [auto build test ERROR on sparc/master] [also build test ERROR on v4.5-rc6] [cannot apply to next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https

Re: [PATCH] sparc64: Add support for Application Data Integrity (ADI)

On 03/02/2016 01:26 PM, kbuild test robot wrote: Hi Khalid, [auto build test ERROR on sparc/master] [also build test ERROR on v4.5-rc6] [cannot apply to next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https

Re: [PATCH v10 07/12] task_isolation: add debug boot flag

On Wed, Mar 02, 2016 at 03:09:31PM -0500, Chris Metcalf wrote: > +void task_isolation_debug(int cpu) > +{ > + struct task_struct *p; > + > + if (!task_isolation_possible(cpu)) > + return; > + > + rcu_read_lock(); > + p = cpu_curr(cpu); > + get_task_struct(p); As I

Re: [PATCH v10 07/12] task_isolation: add debug boot flag

On Wed, Mar 02, 2016 at 03:09:31PM -0500, Chris Metcalf wrote: > +void task_isolation_debug(int cpu) > +{ > + struct task_struct *p; > + > + if (!task_isolation_possible(cpu)) > + return; > + > + rcu_read_lock(); > + p = cpu_curr(cpu); > + get_task_struct(p); As I

Re: linux-next: unsigned commits in tpmdd tree

Hi Jarkko, On Wed, 2 Mar 2016 16:29:56 +0200 Jarkko Sakkinen wrote: > > On Wed, Mar 02, 2016 at 07:42:18AM +1100, Stephen Rothwell wrote: > > Hi Jarkko, > > > > All the new commits in you tree today have no Signed-off-by from you as > > the committer. > >

Re: linux-next: unsigned commits in tpmdd tree

Hi Jarkko, On Wed, 2 Mar 2016 16:29:56 +0200 Jarkko Sakkinen wrote: > > On Wed, Mar 02, 2016 at 07:42:18AM +1100, Stephen Rothwell wrote: > > Hi Jarkko, > > > > All the new commits in you tree today have no Signed-off-by from you as > > the committer. > > Oops :( This is my mistake. Do you

[REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2

Hi David, On Tue, Mar 01, 2016 at 12:07:49PM -0800, Jeremiah Mahler wrote: > Hi all, > > On Tue, Mar 01, 2016 at 08:11:54AM +, Dexuan Cui wrote: > > Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V > > guest, even > > when I didn't configure any NIC for the guest: >

[REGRESSION, bisect] net: ipv6: unregister_netdevice: waiting for lo to become free. Usage count = 2

Hi David, On Tue, Mar 01, 2016 at 12:07:49PM -0800, Jeremiah Mahler wrote: > Hi all, > > On Tue, Mar 01, 2016 at 08:11:54AM +, Dexuan Cui wrote: > > Hi, I got this line every 10 seconds with today's linux-next in a Hyper-V > > guest, even > > when I didn't configure any NIC for the guest: >

Re: [PATCH] sparc64: Add support for Application Data Integrity (ADI)

Hi Khalid, [auto build test ERROR on sparc/master] [also build test ERROR on v4.5-rc6] [cannot apply to next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Khalid-Aziz/sparc64-Add

Re: [PATCH] sparc64: Add support for Application Data Integrity (ADI)

Hi Khalid, [auto build test ERROR on sparc/master] [also build test ERROR on v4.5-rc6] [cannot apply to next-20160302] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Khalid-Aziz/sparc64-Add

[PATCH v10 10/12] arch/tile: enable task isolation functionality

We add the necessary call to task_isolation_enter() in the prepare_exit_to_usermode() routine. We already unconditionally call into this routine if TIF_NOHZ is set, since that's where we do the user_enter() call. We add calls to task_isolation_check_exception() in places where exceptions may not

[PATCH v10 10/12] arch/tile: enable task isolation functionality

We add the necessary call to task_isolation_enter() in the prepare_exit_to_usermode() routine. We already unconditionally call into this routine if TIF_NOHZ is set, since that's where we do the user_enter() call. We add calls to task_isolation_check_exception() in places where exceptions may not

[PATCH v10 02/12] vmstat: add vmstat_idle function

This function checks to see if a vmstat worker is not running, and the vmstat diffs don't require an update. The function is called from the task-isolation code to see if we need to actually do some work to quiet vmstat. Acked-by: Christoph Lameter Signed-off-by: Chris Metcalf

[PATCH v10 02/12] vmstat: add vmstat_idle function

This function checks to see if a vmstat worker is not running, and the vmstat diffs don't require an update. The function is called from the task-isolation code to see if we need to actually do some work to quiet vmstat. Acked-by: Christoph Lameter Signed-off-by: Chris Metcalf ---

Re: [GIT PULL] ARM: EXYNOS: dts for 4.6, 2nd pull

On Tuesday 01 March 2016 18:37:20 Krzysztof Kozlowski wrote: > > Second pull request with DT changes for v4.6. > This is on top of previous DT changes Pulled into next/dt, thanks! Arnd

[PATCH RT 7/7] Linux 3.4.110-rt140-rc1

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 3/7] kernel: softirq: unlock with irqs on

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior We unlock the lock while the interrupts are off. This isn't a problem now but will get because the migrate_disable() + enable are

Re: [GIT PULL] ARM: EXYNOS: dts for 4.6, 2nd pull

On Tuesday 01 March 2016 18:37:20 Krzysztof Kozlowski wrote: > > Second pull request with DT changes for v4.6. > This is on top of previous DT changes Pulled into next/dt, thanks! Arnd

[PATCH RT 7/7] Linux 3.4.110-rt140-rc1

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: "Steven Rostedt (Red Hat)" --- localversion-rt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/localversion-rt b/localversion-rt index

[PATCH RT 3/7] kernel: softirq: unlock with irqs on

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior We unlock the lock while the interrupts are off. This isn't a problem now but will get because the migrate_disable() + enable are not symmetrical in

Re: Question about prio_changed_dl()

On Wed, 2 Mar 2016 20:02:58 +0100 Peter Zijlstra wrote: > On Sat, Feb 27, 2016 at 12:37:57PM +0100, luca abeni wrote: > > Subject: sched/core: fix __sched_setscheduler() to properly invoke > > prio_changed_dl() > > > > Currently, prio_changed_dl() is not called when

Re: Question about prio_changed_dl()

On Wed, 2 Mar 2016 20:02:58 +0100 Peter Zijlstra wrote: > On Sat, Feb 27, 2016 at 12:37:57PM +0100, luca abeni wrote: > > Subject: sched/core: fix __sched_setscheduler() to properly invoke > > prio_changed_dl() > > > > Currently, prio_changed_dl() is not called when __sched_setscheduler() > >

[PATCH] hid: thingm: change driver to use RGB LED core extension

Based on the proposed RGB LED core extension the thingm driver was changed to make use of this extension. It allows to simplify the code a lot. For now primary purpose of this patch is to facilitate testing of the RGB LED core extension. I didn't find a way to split the patch into smaller parts

[PATCH] hid: thingm: change driver to use RGB LED core extension

Based on the proposed RGB LED core extension the thingm driver was changed to make use of this extension. It allows to simplify the code a lot. For now primary purpose of this patch is to facilitate testing of the RGB LED core extension. I didn't find a way to split the patch into smaller parts

[PATCH RT 6/7] kernel: sched: Fix preempt_disable_ip recodring for preempt_disable()

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior preempt_disable() invokes preempt_count_add() which saves the caller in current->preempt_disable_ip. It uses CALLER_ADDR1 which

[PATCH RT 4/7] trace: Use rcuidle version for preemptoff_hist trace point

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6

[PATCH RT 6/7] kernel: sched: Fix preempt_disable_ip recodring for preempt_disable()

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior preempt_disable() invokes preempt_count_add() which saves the caller in current->preempt_disable_ip. It uses CALLER_ADDR1 which does not look for its

[PATCH RT 4/7] trace: Use rcuidle version for preemptoff_hist trace point

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Yang Shi When running -rt kernel with both PREEMPT_OFF_HIST and LOCKDEP enabled, the below error is reported: [ INFO: suspicious RCU usage. ] 4.4.1-rt6 #1 Not tainted

[PATCH RT 2/7] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion

[PATCH RT 5/7] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian

[PATCH RT 0/7] Linux 3.4.110-rt140-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.4.110-rt140-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH RT 2/7] kernel: migrate_disable() do fastpath in atomic & irqs-off

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior With interrupts off it makes no sense to do the long path since we can't leave the CPU anyway. Also we might end up in a recursion with lockdep.

[PATCH RT 5/7] rcu/torture: Comment out rcu_bh ops on PREEMPT_RT_FULL

3.4.110-rt140-rc1 stable review patch. If anyone has any objections, please let me know. -- From: Clark Williams RT has dropped support of rcu_bh, comment out in rcutorture. Signed-off-by: Clark Williams Signed-off-by: Sebastian Andrzej Siewior Signed-off-by: Thomas Gleixner

[PATCH RT 0/7] Linux 3.4.110-rt140-rc1

Dear RT Folks, This is the RT stable review cycle of patch 3.4.110-rt140-rc1. Please scream at me if I messed something up. Please test the patches too. The -rc release will be uploaded to kernel.org and will be deleted when the final release is out. This is just a review release (or release

[PATCH v10 04/12] task_isolation: add initial support

The existing nohz_full mode is designed as a "soft" isolation mode that makes tradeoffs to minimize userspace interruptions while still attempting to avoid overheads in the kernel entry/exit path, to provide 100% kernel semantics, etc. However, some applications require a "hard" commitment from

[PATCH v10 04/12] task_isolation: add initial support

The existing nohz_full mode is designed as a "soft" isolation mode that makes tradeoffs to minimize userspace interruptions while still attempting to avoid overheads in the kernel entry/exit path, to provide 100% kernel semantics, etc. However, some applications require a "hard" commitment from

[PATCH v10 05/12] task_isolation: support CONFIG_TASK_ISOLATION_ALL

This option, similar to NO_HZ_FULL_ALL, simplifies configuring a system to boot by default with all cores except the boot core running in task isolation mode. --- init/Kconfig | 10 ++ kernel/isolation.c | 6 ++ 2 files changed, 16 insertions(+) diff --git a/init/Kconfig

Re: [tip:smp/hotplug] rcu: Make CPU_DYING_IDLE an explicit call

On Tue, Mar 01, 2016 at 11:58:59AM -0800, tip-bot for Thomas Gleixner wrote: > Commit-ID: 27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0 > Gitweb: http://git.kernel.org/tip/27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0 > Author: Thomas Gleixner > AuthorDate: Fri, 26 Feb 2016

Re: [tip:smp/hotplug] rcu: Make CPU_DYING_IDLE an explicit call

On Tue, Mar 01, 2016 at 11:58:59AM -0800, tip-bot for Thomas Gleixner wrote: > Commit-ID: 27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0 > Gitweb: http://git.kernel.org/tip/27d50c7eeb0f03c3d3ca72aac4d2dd487ca1f3f0 > Author: Thomas Gleixner > AuthorDate: Fri, 26 Feb 2016 18:43:44 + >

[PATCH v10 05/12] task_isolation: support CONFIG_TASK_ISOLATION_ALL

This option, similar to NO_HZ_FULL_ALL, simplifies configuring a system to boot by default with all cores except the boot core running in task isolation mode. --- init/Kconfig | 10 ++ kernel/isolation.c | 6 ++ 2 files changed, 16 insertions(+) diff --git a/init/Kconfig

[PATCH v10 07/12] task_isolation: add debug boot flag

The new "task_isolation_debug" flag simplifies debugging of TASK_ISOLATION kernels when processes are running in PR_TASK_ISOLATION_ENABLE mode. Such processes should get no interrupts from the kernel, and if they do, when this boot flag is specified a kernel stack dump on the console is

[PATCH v10 07/12] task_isolation: add debug boot flag

The new "task_isolation_debug" flag simplifies debugging of TASK_ISOLATION kernels when processes are running in PR_TASK_ISOLATION_ENABLE mode. Such processes should get no interrupts from the kernel, and if they do, when this boot flag is specified a kernel stack dump on the console is

[PATCH v10 03/12] lru_add_drain_all: factor out lru_add_drain_needed

This per-cpu check was being done in the loop in lru_add_drain_all(), but having it be callable for a particular cpu is helpful for the task-isolation patches. Signed-off-by: Chris Metcalf --- include/linux/swap.h | 1 + mm/swap.c| 15 ++- 2 files

[PATCH v10 03/12] lru_add_drain_all: factor out lru_add_drain_needed

This per-cpu check was being done in the loop in lru_add_drain_all(), but having it be callable for a particular cpu is helpful for the task-isolation patches. Signed-off-by: Chris Metcalf --- include/linux/swap.h | 1 + mm/swap.c| 15 ++- 2 files changed, 11

[PATCH v10 09/12] arch/x86: enable task isolation functionality

In prepare_exit_to_usermode(), call task_isolation_ready() when we are checking the thread-info flags, and after we've handled the other work, call task_isolation_enter() unconditionally. In syscall_trace_enter_phase1(), we add the necessary support for strict-mode detection of syscalls. We add

[PATCH v10 12/12] arch/arm64: enable task isolation functionality

In do_notify_resume(), call task_isolation_ready() when we are checking the thread-info flags; and after we've handled the other work, call task_isolation_enter() unconditionally. To ensure we always call task_isolation_enter() when returning to userspace, modify _TIF_WORK_MASK to be _TIF_NOHZ,

[PATCH v10 08/12] arm, tile: turn off timer tick for oneshot_stopped state

When the schedule tick is disabled in tick_nohz_stop_sched_tick(), we call hrtimer_cancel(), which eventually calls down into __remove_hrtimer() and thus into hrtimer_force_reprogram(). That function's call to tick_program_event() detects that we are trying to set the expiration to KTIME_MAX and

[PATCH v10 09/12] arch/x86: enable task isolation functionality

In prepare_exit_to_usermode(), call task_isolation_ready() when we are checking the thread-info flags, and after we've handled the other work, call task_isolation_enter() unconditionally. In syscall_trace_enter_phase1(), we add the necessary support for strict-mode detection of syscalls. We add

[PATCH v10 12/12] arch/arm64: enable task isolation functionality

In do_notify_resume(), call task_isolation_ready() when we are checking the thread-info flags; and after we've handled the other work, call task_isolation_enter() unconditionally. To ensure we always call task_isolation_enter() when returning to userspace, modify _TIF_WORK_MASK to be _TIF_NOHZ,

[PATCH v10 08/12] arm, tile: turn off timer tick for oneshot_stopped state

When the schedule tick is disabled in tick_nohz_stop_sched_tick(), we call hrtimer_cancel(), which eventually calls down into __remove_hrtimer() and thus into hrtimer_force_reprogram(). That function's call to tick_program_event() detects that we are trying to set the expiration to KTIME_MAX and

[PATCH v10 11/12] arm64: factor work_pending state machine to C

Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc state machine that can be difficult to reason about due to duplicated code and a large number of branch targets. This patch factors the common logic out into the existing do_notify_resume function, converting the code to C

[PATCH v10 06/12] task_isolation: support PR_TASK_ISOLATION_STRICT mode

With task_isolation mode, the task is in principle guaranteed not to be interrupted by the kernel, but only if it behaves. In particular, if it enters the kernel via system call, page fault, or any of a number of other synchronous traps, it may be unexpectedly exposed to long latencies. Add a

[PATCH v10 06/12] task_isolation: support PR_TASK_ISOLATION_STRICT mode

With task_isolation mode, the task is in principle guaranteed not to be interrupted by the kernel, but only if it behaves. In particular, if it enters the kernel via system call, page fault, or any of a number of other synchronous traps, it may be unexpectedly exposed to long latencies. Add a

[PATCH v10 11/12] arm64: factor work_pending state machine to C

Currently ret_fast_syscall, work_pending, and ret_to_user form an ad-hoc state machine that can be difficult to reason about due to duplicated code and a large number of branch targets. This patch factors the common logic out into the existing do_notify_resume function, converting the code to C

[PATCH v10 00/12] support "task_isolation" mode

Here is the latest version of the task-isolation patch set, adopting various suggestions made about the v9 patch series, including some feedback from testing on the new EZchip NPS ARC platform (although the new arch/arc support is not included in this patch series). All of the suggestions were

[PATCH v10 00/12] support "task_isolation" mode

Here is the latest version of the task-isolation patch set, adopting various suggestions made about the v9 patch series, including some feedback from testing on the new EZchip NPS ARC platform (although the new arch/arc support is not included in this patch series). All of the suggestions were

[PATCH v10 01/12] vmstat: add quiet_vmstat_sync function

In commit f01f17d3705b ("mm, vmstat: make quiet_vmstat lighter") the quiet_vmstat() function became asynchronous, in the sense that the vmstat work was still scheduled to run on the core when the function returned. For task isolation, we need a synchronous version of the function that guarantees

[PATCH v10 01/12] vmstat: add quiet_vmstat_sync function

In commit f01f17d3705b ("mm, vmstat: make quiet_vmstat lighter") the quiet_vmstat() function became asynchronous, in the sense that the vmstat work was still scheduled to run on the core when the function returned. For task isolation, we need a synchronous version of the function that guarantees

Re: [PATCH v2] net: ezchip: adapt driver to little endian architecture

On Wednesday 02 March 2016 21:38:04 Lada Trimasova wrote: > Since ezchip network driver is written with big endian EZChip platform it > is necessary to add support for little endian architecture. > > The first issue is that the order of the bits in a bit field is > implementation specific. So all

Re: [PATCH v2] net: ezchip: adapt driver to little endian architecture

On Wednesday 02 March 2016 21:38:04 Lada Trimasova wrote: > Since ezchip network driver is written with big endian EZChip platform it > is necessary to add support for little endian architecture. > > The first issue is that the order of the bits in a bit field is > implementation specific. So all

Re: [PATCH] net/ipv4: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:38:06 + > 8cc785f6f429c2a3fb81745dc142cbd72a462c4a ("net: ipv4: make the ping > /proc code AF-independent") removed the code using it, but renamed this > variable instead of removing it. > > Signed-off-by: Eric

Re: [PATCH] net/ipv4: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:38:06 + > 8cc785f6f429c2a3fb81745dc142cbd72a462c4a ("net: ipv4: make the ping > /proc code AF-independent") removed the code using it, but renamed this > variable instead of removing it. > > Signed-off-by: Eric Engestrom Applied.

Re: [PATCH] net/rtnetlink: remove dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:36:38 + > 3b766cd832328fcb87db3507e7b98cf42f21689d ("net/core: Add reading VF > statistics through the PF netdevice") added that variable but it's never > been used. > > Signed-off-by: Eric Engestrom

Re: [PATCH] net/rtnetlink: remove dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:36:38 + > 3b766cd832328fcb87db3507e7b98cf42f21689d ("net/core: Add reading VF > statistics through the PF netdevice") added that variable but it's never > been used. > > Signed-off-by: Eric Engestrom Applied.

Re: [PATCH] ethernet/atl1c: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:40:23 + > Left over from c24588afc536a35c924d014f13b669b20ccf8553 > ("atl1c: using fixed TXQ configuration for l2cb and l1c") > > Signed-off-by: Eric Engestrom Applied.

Re: [PATCH] net-sysfs: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:34:25 + > This format hasn't been used since 04ed3e741d0f133e02bed7fa5c98edba128f90e7 > ("net: change netdev->features to u32") > > Signed-off-by: Eric Engestrom A patch that does this is

Re: [PATCH] ethernet/atl1c: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:40:23 + > Left over from c24588afc536a35c924d014f13b669b20ccf8553 > ("atl1c: using fixed TXQ configuration for l2cb and l1c") > > Signed-off-by: Eric Engestrom Applied.

Re: [PATCH] net-sysfs: remove left over dead code

From: Eric Engestrom Date: Mon, 29 Feb 2016 16:34:25 + > This format hasn't been used since 04ed3e741d0f133e02bed7fa5c98edba128f90e7 > ("net: change netdev->features to u32") > > Signed-off-by: Eric Engestrom A patch that does this is already in the networking tree, please always check

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