' absolute symbols, and therefore appear as 'a' in
/proc/kallsyms. Fix this.
Cc: Jan Kiszka <jan.kis...@siemens.com>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
trace-util.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/trace-util.c b/trace-util.c
index 5
On Wed, Oct 05, 2016 at 03:03:44PM -0500, Rob Herring wrote:
> On Wed, Oct 5, 2016 at 1:33 PM, Ulf Hansson wrote:
> > On 23 September 2016 at 22:01, Zach Brown wrote:
> >> Certain board configurations can make highspeed malfunction due to
> >> timing
ned-off-by: Josh Cartwright <jo...@ni.com>
Cc: linux-rt-us...@vger.kernel.org
Cc: Jakub Kicinski <moorr...@wp.pl>
Cc: sta...@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
On Wed, Nov 09, 2016 at 10:08:29AM -0600, Zach Brown wrote:
> On Wed, Nov 09, 2016 at 03:24:24PM +0200, Adrian Hunter wrote:
> > On 08/11/16 22:07, Zach Brown wrote:
> > > On NI 9037 boards the max SDIO frequency is limited by trace lengths
> > > and other layout choices. The max SDIO frequency is
gt;
> Signed-off-by: Michal Simek <michal.si...@xilinx.com>
Reviewed-by: Julia Cartwright <ju...@ni.com>
> but no reg property
> Warning (unit_address_vs_reg): Node /memory has a reg or ranges
> property, but no unit name
>
> Signed-off-by: Michal Simek <michal.si...@xilinx.com>
Reviewed-by: Julia Cartwright <ju...@ni.com>
>
> ---
>
> arch/arm/boot/dts/zyn
jaer <sean.nyekj...@prevas.dk>
Signed-off-by: Josh Cartwright <jo...@ni.com>
Cc: linux-rt-us...@vger.kernel.org
Cc: Jakub Kicinski <moorr...@wp.pl>
Cc: sta...@vger.kernel.org
Cc: linux-ser...@vger.kernel.org
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Signed-off-b
On Thu, Mar 23, 2017 at 10:26:49AM +, Lee Jones wrote:
> On Thu, 23 Mar 2017, Lionel DEBIEVE wrote:
>
> > On 03/22/2017 07:47 PM, Julia Cartwright wrote:
> > > On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
> > >> On 03/22/20
On Thu, Mar 23, 2017 at 09:01:43PM +0100, Heiko St?bner wrote:
> Am Donnerstag, 23. März 2017, 13:29:10 CET schrieb Julia Cartwright:
> > On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> > > Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
>
On Wed, Mar 22, 2017 at 08:44:14AM -0400, William Breathitt Gray wrote:
> On Tue, Mar 21, 2017 at 05:43:07PM -0500, Julia Cartwright wrote:
> >The 104-idi-48 gpio driver currently implements an irq_chip for handling
> >interrupts; due to how irq_chip handling is done,
On Thu, Mar 23, 2017 at 06:55:50PM +0100, Heiko St?bner wrote:
> Am Donnerstag, 23. März 2017, 17:51:53 CET schrieb John Keeping:
> > On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
[..]
> > > [..]
> > >
> > > > @@ -1185,17 +1177,14 @@ stat
On Wed, Mar 22, 2017 at 01:30:12PM -0500, Grygorii Strashko wrote:
>
> On 03/22/2017 01:01 PM, Steven Rostedt wrote:
> > On Wed, 22 Mar 2017 12:37:59 -0500
> > Julia Cartwright <ju...@ni.com> wrote:
> >
> > > Which kernel were you testing on, here? From
On Wed, Mar 22, 2017 at 10:54:15AM +0100, Julia Lawall wrote:
> On Tue, 21 Mar 2017, Julia Cartwright wrote:
> > On PREEMPT_RT, the spinlock_t type becomes an object which sleeps under
> > contention. The codepaths used to support scheduling (irq dispatching, arch
> > code,
On Wed, Mar 22, 2017 at 04:18:43PM +0100, Lionel Debieve wrote:
> Use raw_spin_lock in enable/disable channel as it comes from
> interrupt context.
>
> BUG: sleeping function called from invalid context at
> kernel/locking/rtmutex.c:995
> in_atomic(): 1, irqs_disabled(): 128, pid: 307, name:
Hello John-
One quick question below. Apologies if this has been covered, but just
want to be sure.
On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote:
> regmap_update_bits does its own locking and everything else accessed
> here is a local variable so there is no need to lock around
Hello RT Folks,
I'm happy to announce the 4.1.39-rt47 stable release.
This release is just an update to the new stable 4.1.39 version and no
RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
..@ellerman.id.au>
Cc: Segher Boessenkool <seg...@kernel.crashing.org>
Tested-by: Aaro Koskinen <aaro.koski...@iki.fi>
Acked-by: Olof Johansson <o...@lixom.net>
Signed-off-by: Michael Ellerman <m...@ellerman.id.au>
Signed-off-by: Julia Cartwright <ju...@ni.com>
-
e raw spinlock variants") as an
example of _one_ such instance, which fixed a real bug seen in the field.
Cc: Thomas Gleixner <t...@linutronix.de>
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Cc: Linus Walleij <linus.wall...@linaro.org>
Signed-off-by: Julia Cartwright
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Acked-for-MFD-by: Lee Jones <lee.jo...@linaro.org>
Signed-off-by: Julia Cartwright <j
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Acked-for-MFD-by: Lee Jones <lee.jo...@linaro.org>
Signed-off-by: Julia Cartwright <j
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
v1 -> v2:
- Add hunk which p
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
v1 -> v2:
- No change.
arch/pow
s Palix <nicolas.pa...@imag.fr>
Cc: Michal Marek <mma...@suse.com>
Cc: Lee Jones <lee.jo...@linaro.org>
Cc: co...@systeme.lip6.fr
--
Julia Cartwright (9):
Coccinelle: locks: identify callers of spin_lock{,_irq,_irqsave}() in
irqchip implementations
alpha: mar
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Acked-for-MFD-by: Lee Jones <lee.jo...@linaro.org>
Signed-off-by: Julia Cartwright <j
lock w/ RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
New patch as of v2 of series.
d
lock w/ RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
New patch as of v2 of series.
d
lock w/ RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
New patch as of v2 of series.
d
Hello John-
On Wed, Mar 15, 2017 at 05:46:52PM +, John Keeping wrote:
> This lock is used from rockchip_irq_set_type() which is part of the
> irq_chip implementation and thus must use raw_spinlock_t as documented
> in Documentation/gpio/driver.txt.
>
> Signed-off-by: John Keeping
t; > spinlock since with full RT preemption the regmap's spinlock may sleep.
>
> Nice work! It all looks good to me, let's see what Heiko says.
>
> Please keep Julia Cartwright on the CC for this patch series, she is
> doing some coccinelle-based rewrites to use raw spinlocks
On Wed, Mar 15, 2017 at 11:17:44AM +, Lee Jones wrote:
> On Thu, 09 Mar 2017, Julia Cartwright wrote:
>
> > The t7l66xb mfd driver currently implements an irq_chip for handling
> > interrupts; due to how irq_chip handling is done, it's necessary for the
> > irq_chip me
On Wed, Mar 15, 2017 at 07:16:53PM +0100, Heiko Stuebner wrote:
> Am Mittwoch, 15. März 2017, 18:08:06 CET schrieb John Keeping:
> > On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> > > On Wed, Mar 15, 2017 at 05:46:52PM +, John Keeping wrote:
> > &g
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/pinctrl/sunxi/pinc
lock w/ RT kernels, it is not suitable to be used with
irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gpio-10
lock w/ RT kernels, it is not suitable to be used with
irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/pinctrl/sirf/pinct
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/mfd
lock w/ RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/i2c/muxes/i2c-mu
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gpio-zx.c | 24 +++
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
arch/powerpc/platforms/52xx/mp
RT
kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gp
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/g
e raw spinlock variants") as an
example of _one_ such instance, which fixed a real bug seen in the field.
Cc: Thomas Gleixner <t...@linutronix.de>
Cc: Sebastian Andrzej Siewior <bige...@linutronix.de>
Cc: Linus Walleij <linus.wall...@linaro.org>
Signed-off-by: Julia Cartwright <ju
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/g
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gpi
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
arch/alpha/include/asm/core_marvel
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/pinctrl/bcm/pinctrl-i
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/mfd/t7l66xb.c | 20 +++
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/pinctrl/pi
<bige...@linutronix.de>
Cc: Linus Walleij <linus.wall...@linaro.org>
Cc: Julia Lawall <julia.law...@lip6.fr>
Cc: Gilles Muller <gilles.mul...@lip6.fr>
Cc: Nicolas Palix <nicolas.pa...@imag.fr>
Cc: Michal Marek <mma...@suse.com>
Cc: co...@systeme.lip6.fr
-
Julia Cart
lock w/ RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gpio
RT kernels, it is not suitable to be used with irq_chips.
A quick audit of the operations under the lock reveal that they do only
minimal, bounded work, and are therefore safe to do under a raw spinlock.
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/gpio/gpi
Hello Julia-
Thanks for the feedback.
On Thu, Mar 09, 2017 at 09:15:21PM +0100, Julia Lawall wrote:
> > +@match2 depends on match@
> > +identifier match.__irq_mask;
> > +identifier data;
> > +identifier x;
> > +identifier l;
> > +type T;
> > +position j0;
> > +expression flags;
> > +@@
> > +
: avoid wbinvd() for PREEMPT
Julia Cartwright (2):
pinctrl: qcom: Use raw spinlock variants
Linux 4.1.38-rt46
Mike Galbraith (1):
cpuset: Convert callback_lock to raw_spinlock_t
Sebastian Andrzej Siewior (3):
radix-tree: use local locks
rt: Drop mutex_disable
On Fri, Mar 10, 2017 at 09:28:08AM -0800, Ray Jui wrote:
> Hi Julia/Linus,
>
> On 3/9/2017 8:21 AM, Julia Cartwright wrote:
> > The bcm-kona gpio driver currently implements an irq_chip for handling
> > interrupts; due to how irq_chip handling is done, it's necessary for the
changelog]
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit a88182f3f1818407d738e832650085110cae1f29)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
include/linux/module.h | 5 +
kernel/module.c| 5 +
2 files changed, 10 insertio
: Fix compilation error for !CONFIG_MODULES and !CONFIG_SMP
John Ogness (1):
x86/mm/cpa: avoid wbinvd() for PREEMPT
Julia Cartwright (2):
pinctrl: qcom: Use raw spinlock variants
Linux 4.1.38-rt46-rc1
Mike Galbraith (1):
cpuset: Convert callback_lock to raw_spinlock_t
Sebastian Andrzej
58cbba1a32b043a842f205a631f)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
include/linux/mutex_rt.h | 5 +
kernel/locking/rtmutex.c | 3 +--
2 files changed, 6 insertions(+), 2 deletions(-)
diff --git a/include/linux/mutex_rt.h b/include/linux/mutex_rt.h
index c38a44b14da5..e0284e
is not required.
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit 5dbe8fd80a2ccfc8c24874e19259df51d91e02a2)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/locking/rtmutex.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
<efa...@gmx.de>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit 5625380ec638bdc89813f0bac9d1e431514e8a19)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/cpuset.c | 66 ---
4.1.38-rt46-rc1 stable review patch.
If you have any objection to the inclusion of this patch, let me know.
--- 8< --- 8< --- 8< ---
From: Julia Cartwright <ju...@ni.com>
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/
tronix.de>
(cherry picked from commit b2ee2b3e4642646571fa2368c350278b6b9d991b)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
include/linux/module.h | 1 +
include/linux/percpu.h | 1 +
kernel/locking/lockdep.c | 33 +++--
kernel/module.c |
ronix.de>
(cherry picked from commit 682d58995008862febd37bbab89e33e38da84cc4)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
include/linux/radix-tree.h | 12 ++--
lib/radix-tree.c | 22 ++
2 files changed, 16 insertions(+), 18 deletions(-)
diff --g
4.1.38-rt46-rc1 stable review patch.
If you have any objection to the inclusion of this patch, let me know.
--- 8< --- 8< --- 8< ---
From: Julia Cartwright <ju...@ni.com>
The MSM pinctrl driver currently implements an irq_chip for handling
GPIO interrupts; due to how irq_chip h
ble...@vger.kernel.org
Acked-by: Peter Zijlstra (Intel) <pet...@infradead.org>
Signed-off-by: John Ogness <john.ogn...@linutronix.de>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit 9e539d7327b265c639c859ab1fb7d3699ba0cb19)
Signed-off-by:
Hello RT Folks,
I'm happy to announce the 4.1.42-rt49 stable release.
This release is just an update to the new stable 4.1.42 version and no
RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
On Tue, Jun 27, 2017 at 05:47:41AM +, Feng Feng24 Liu wrote:
> Hi, Julia
> Thanks for your kindly hit. I will try this patch
> The problem is accidental. I will try to reproduce it.
> BTW, could you help to give the link about the emails which
> discuss about " nsfs:
.ru>
Tested-by: Alexander GQ Gerasiov <g...@redlab-i.ru>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
Hey All-
While this fixes a problem on RT primarily, the patch is equally applicable
upstream, as such probably makes sense to be pulled through the md tree. It
may also make
On Fri, Aug 04, 2017 at 04:56:51PM -0500, Haris Okanovic wrote:
> I have a latency issue using a SPI-based TPM chip with tpm_tis driver
> from non-rt usermode application, which induces ~400 us latency spikes
> in cyclictest (Intel Atom E3940 system, PREEMPT_RT_FULL kernel).
>
> The spikes are
RRUPTIBLE.
Use signal_pending_state() unconditionaly.
Cc: rt-sta...@vger.kernel.org
Signed-off-by: Thomas Gleixner <t...@linutronix.de>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit 9edcb2cd71ff3684755f52129538260efa382789)
Signed-off-by: Jul
ano <daniel.lezc...@linaro.org>
Cc: linux-rt-users <linux-rt-us...@vger.kernel.org>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit df0fba5ba4c69cdc68bdaa5ca7a4100d959fdd07)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/cpu_pm.
:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/incr/patch-4.1.42-rt49-rt50-rc1.patch.xz
Alex Shi (1):
cpu_pm: replace raw_notifier to atomic_notifier
Julia Cartwright (1):
Linux 4.1.42-rt50-rc1
Peter Zijlstra (2
4.1.42-rt50-rc1 stable review patch.
If you have any objection to the inclusion of this patch, let me know.
--- 8< --- 8< --- 8< ---
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 4b7dca68a5b4..e8a9a36bb066 100644
Thomas Gleixner <t...@linutronix.de>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit 2f9f24e15088d2ef3244d088a9604d7e98c9c625)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/sched/core.c | 2 +-
1 file changed, 1 insertion(+), 1
stable...@vger.kernel.org
Acked-by: Thomas Gleixner <t...@linutronix.de>
Signed-off-by: Peter Zijlstra (Intel) <pet...@infradead.org>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit a1762267d95649bddf6e94e7e3305e0207d0fff0)
Signed-off
ed-off-by: Thomas Gleixner <t...@linutronix.de>
(cherry picked from commit c9fe9196079f738c89c3ffcdce3fbe142ac3f3c4)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
include/linux/smp.h | 12
init/main.c | 8
kernel/module.c | 6 +-
mm/perc
by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/incr/patch-4.1.42-rt49-rt50.patch.xz
Enjoy!
Julia
Changes from v4.1.42-rt49:
---
Alex Shi (1):
cpu_pm: replace raw_notifier to atomic_notifier
Julia Cartwright (1):
Linux 4.1.42-rt50
Peter
On Thu, Aug 17, 2017 at 09:30:28AM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-08-16 15:42:28 [-0500], Julia Cartwright wrote:
[..]
> > diff --git a/kernel/cpu_pm.c b/kernel/cpu_pm.c
> > index 9656a3c36503..9da42f83ee03 100644
> > --- a/kernel/cpu_pm.c
> > +++ b/ke
On Mon, Jun 26, 2017 at 04:54:36PM +0200, Sebastian Andrzej Siewior wrote:
> On 2017-06-26 10:24:18 [-0400], Steven Rostedt wrote:
> > > CPU: 17 PID: 1738811 Comm: ip Not tainted 4.4.70-thinkcloud-nfv #1
> > > Hardware name: LENOVO System x3650 M5: -[8871AC1]-/01GR174, BIOS
> > >
Hello RT Folks,
I'm happy to announce the 4.1.40-rt48 stable release.
This release is just an update to the new stable 4.1.40 version and no
RT specific changes have been made.
You can get this release via the git tree at:
git://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git
On Tue, Sep 05, 2017 at 04:57:49PM -0500, Tom Zanussi wrote:
> Add background and details on inter-event hist triggers, including
> hist variables, synthetic events, and actions.
>
> Signed-off-by: Tom Zanussi
> Signed-off-by: Baohong Liu
>
pin_lock
> <-vprintk_emit
> [512258.614119] sm-3297 16 d...112 359465349138789: log_store <-vprintk_emit
> [512258.614127] sm-3297 16 .12 359465349139068: migrate_disable
> <-vprintk_emit
>
> According to a discussion (see Link: below) on the linux-rt-users
On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> On Thu, 5 Oct 2017 10:37:59 -0500
> Julia Cartwright <ju...@ni.com> wrote:
>
> > On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> > > On Thu, 5 Oct 2017, Julia Cartwright wrote:
On Thu, Oct 05, 2017 at 06:16:23PM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Julia Cartwright wrote:
>
> > On Thu, Oct 05, 2017 at 11:55:39AM -0400, Steven Rostedt wrote:
> > > On Thu, 5 Oct 2017 10:37:59 -0500
> > > Julia Cartwright <ju...@ni.com>
On Thu, Oct 05, 2017 at 05:27:30PM +0200, Thomas Gleixner wrote:
> On Thu, 5 Oct 2017, Julia Cartwright wrote:
> > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > > - preempt_disable();
> > > + preempt_disable_nort();
> > >
On Thu, Oct 05, 2017 at 01:53:05PM -0300, Arnaldo Carvalho de Melo wrote:
> Em Thu, Oct 05, 2017 at 09:17:44AM -0500, Julia Cartwright escreveu:
> > On Tue, Oct 03, 2017 at 12:49:19PM -0300, Arnaldo Carvalho de Melo wrote:
> > > +++ b/drivers/infiniband/hw/hfi1/pio.c
> &
Hey Thomas, Peter-
Gratian and I have been debugging into a nasty and difficult race w/
futexes seemingly the culprit. The original symptom we were seeing
was a seemingly spurious -EDEADLK from a futex(LOCK_PI) operation.
On further analysis, however, it appears the thread which gets the
by applying the incremental patch:
http://www.kernel.org/pub/linux/kernel/projects/rt/4.1/incr/patch-4.1.46-rt51-rt52.patch.xz
Enjoy!
Julia
Changes from v4.1.46-rt51:
---
Julia Cartwright (2):
workqueue: fixup rcu check for RT
Linux 4.1.46-rt52
Sebastian Andrzej Siewior (2):
PM
<bige...@linutronix.de>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/workqueue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 6bdcab98501c..90e261c8811e 100644
--- a/kernel/workqueue.c
+++ b/kernel/workqueue
re is the delta.
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit f648e23dac72deef07f25e05fc09dbbc209dbd33)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/cpu_pm.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/kernel
...@gmx.de>
Tested-by: Mike Galbraith <efa...@gmx.de>
Signed-off-by: Sebastian Andrzej Siewior <bige...@linutronix.de>
(cherry picked from commit b3c08bffdcdd23f1b3ca8d9c01e3b8a715e03d46)
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
kernel/time/hrtimer.c | 5 +
1 fi
4.1.46-rt52-rc1 stable review patch.
If you have any objection to the inclusion of this patch, let me know.
--- 8< --- 8< --- 8< ---
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 75493460c41f..d42746076d9b 100644
incr/patch-4.1.46-rt51-rt52-rc1.patch.xz
Julia Cartwright (2):
workqueue: fixup rcu check for RT
Linux 4.1.46-rt52-rc1
Sebastian Andrzej Siewior (2):
PM / CPU: replace raw_notifier with atomic_notifier (fixup)
kernel/hrtimer: migrate deferred timer on CPU down
kernel/cpu_pm.c
;t...@linutronix.de>
Cc: Ingo Molnar <mi...@redhat.com>
Cc: Peter Zijlstra <pet...@infradead.org>
Cc: Darren Hart <dvh...@infradead.org>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
I'm not sure my analysis is 100% correct here, so please carefully think
throug
et: macb: Added support for RX filtering")
Cc: Rafal Ozieblo <raf...@cadence.com>
Cc: Julia Lawall <julia.law...@lip6.fr>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
While Julia Lawall's cocci-generated patch fixes the problem, the right
solution is to obviate the pro
The list_for_each_entry() macro already handles the case where the list
is empty (by not executing the loop body). It's not necessary to handle
this case specially, so stop doing so.
Cc: Rafal Ozieblo <raf...@cadence.com>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
This is a
,
and tries to be intelligent about the intent of specific arguments (for
example, waking operations use 'val' as an integer count, not just an
arbitrary value).
It doesn't do a full decode of the FUTEX_WAKE_OP's 'val3' argument,
however, this is a good starting point.
Signed-off-by: Julia Cartwright
et: macb: Added support for RX filtering")
Cc: Rafal Ozieblo <raf...@cadence.com>
Cc: Julia Lawall <julia.law...@lip6.fr>
Acked-by: Nicolas Ferre <nicolas.fe...@microchip.com>
Signed-off-by: Julia Cartwright <ju...@ni.com>
---
drivers/net/ethernet/cadence/macb_main
Now that the rx_fs_lock is no longer held across allocation, it's safe
to use GFP_KERNEL for allocating new entries.
This reverts commit 81da3bf6e3f88 ("net: macb: change GFP_KERNEL to
GFP_ATOMIC").
Cc: Julia Lawall <julia.law...@lip6.fr>
Signed-off-by: Julia Cartwrig
The list_for_each_entry() macro already handles the case where the list
is empty (by not executing the loop body). It's not necessary to handle
this case specially, so stop doing so.
Cc: Rafal Ozieblo <raf...@cadence.com>
Acked-by: Nicolas Ferre <nicolas.fe...@microchip.com>
Signed-o
Here's a proper patchset based on net-next.
v1 -> v2:
- Rebased on net-next
- Add Nicolas's Acks
- Reorder commits, putting the list_empty() cleanups prior to the
others.
- Added commit reverting the GFP_ATOMIC change.
Julia Cartwright (3):
net: macb: kill useless use of list_em
1 - 100 of 314 matches
Mail list logo