From: Mark Rutland <mark.rutland@arm.com>
To: "Paul E. McKenney" <paulmck@linux.ibm.com>
Cc: linux@arm.linux.org.uk, dietmar.eggemann@arm.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH arm] Use common outgoing-CPU-notification code
Date: Wed, 26 Jun 2019 17:42:00 +0100 [thread overview]
Message-ID: <20190626164159.GI20635@lakrids.cambridge.arm.com> (raw)
In-Reply-To: <20190617130657.GL26519@linux.ibm.com>
On Mon, Jun 17, 2019 at 06:06:57AM -0700, Paul E. McKenney wrote:
> On Mon, Jun 17, 2019 at 12:58:19PM +0100, Mark Rutland wrote:
> > On Tue, Jun 11, 2019 at 12:24:10PM -0700, Paul E. McKenney wrote:
> > > This commit removes the open-coded CPU-offline notification with new
> > > common code. In particular, this change avoids calling scheduler code
> > > using RCU from an offline CPU that RCU is ignoring. This is a minimal
> > > change. A more intrusive change might invoke the cpu_check_up_prepare()
> > > and cpu_set_state_online() functions at CPU-online time, which would
> > > allow onlining throw an error if the CPU did not go offline properly.
> > >
> > > Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
> > > Cc: linux-arm-kernel@lists.infradead.org
> > > Cc: Russell King <linux@arm.linux.org.uk>
> > > Cc: Mark Rutland <mark.rutland@arm.com>
> > > Tested-by: Dietmar Eggemann <dietmar.eggemann@arm.com>
> >
> > FWIW:
> >
> > Acked-by: Mark Rutland <mark.rutland@arm.com>
> >
> > On the assumption that Russell is ok with this, I think this should be
> > dropped into the ARM patch system [1].
> >
> > Paul, are you familiar with that, or would you prefer that someone else
> > submits the patch there? I can do so if you'd like.
>
> I never have used this system, so please do drop it in there! Let me
> know when you have done so, and I will then drop it from -rcu.
After testing that multi_v7_defconfig built, I've just submitted this as
8872/1:
https://www.armlinux.org.uk/developer/patches/viewpatch.php?id=8872/1
Thanks,
Mark.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-06-26 16:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 19:24 [PATCH arm] Use common outgoing-CPU-notification code Paul E. McKenney
2019-06-17 11:58 ` Mark Rutland
2019-06-17 13:06 ` Paul E. McKenney
2019-06-26 16:42 ` Mark Rutland [this message]
2019-06-26 17:49 ` Paul E. McKenney
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=20190626164159.GI20635@lakrids.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=paulmck@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).