From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Thavatchai Makphaibulchoke <thavatchai.makpahibulchoke@hp.com>,
Thavatchai Makphaibulchoke <tmac@hp.com>, <rostedt@goodmis.org>,
<linux-kernel@vger.kernel.org>, <mingo@redhat.com>,
<tglx@linutronix.de>, <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH RT v2] kernel/res_counter.c: Change lock of struct res_counter to raw_spinlock_t
Date: Fri, 20 Feb 2015 13:53:24 -0500 [thread overview]
Message-ID: <54E782A4.3030502@windriver.com> (raw)
In-Reply-To: <20150218110552.GE28763@linutronix.de>
On 2015-02-18 06:05 AM, Sebastian Andrzej Siewior wrote:
> * Paul Gortmaker | 2015-02-13 16:30:17 [-0500]:
>
> there is the thread "[v3.10-rt / v3.12-rt] scheduling while atomic in
> cgroup code" where I applied Mike's patch. This should fix the problem
> reported and be part of the next release.
> Could please double check (either by grabing the patch or waiting for
> the next release).
I've applied Mike's patch from here:
https://lkml.org/lkml/2014/6/21/11
and tested it on the old dell core2 that reliably showed the splat
at boot, and it is now gone. This is on vanilla 3.14-rt plus isci
fix + simpleworkqueue + aio-swq fix (all pending for 3.18-rt next).
I also tested it on the 20 core canoe pass where the rawlock
conversion patch from Thavatchai caused strange and unpredictable
failure modes and that box seems fine with this smaller footprint
cpulight change.
Paul.
--
>
> Sebastian
>
prev parent reply other threads:[~2015-02-20 18:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-08 19:38 [PATCH RT] kernel/res_counter.c: Change lock of struct res_counter to raw_spinlock_t Thavatchai Makphaibulchoke
2015-01-30 18:59 ` [PATCH RT v2] " Thavatchai Makphaibulchoke
2015-02-13 19:19 ` Paul Gortmaker
2015-02-13 21:21 ` Thavatchai Makphaibulchoke
2015-02-13 21:30 ` Paul Gortmaker
2015-02-18 11:05 ` Sebastian Andrzej Siewior
2015-02-20 18:53 ` Paul Gortmaker [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54E782A4.3030502@windriver.com \
--to=paul.gortmaker@windriver.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=thavatchai.makpahibulchoke@hp.com \
--cc=tmac@hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox