From: joe.korty@concurrent-rt.com
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] 4.4.86-rt99: fix sync breakage between nr_cpus_allowed and cpus_allowed
Date: Wed, 29 Nov 2017 09:24:48 -0500 [thread overview]
Message-ID: <20171129142448.GA18507@zipoli.concurrent-rt.com> (raw)
In-Reply-To: <20171128192234.53d685d4@gandalf.local.home>
On Tue, Nov 28, 2017 at 07:22:34PM -0500, Steven Rostedt wrote:
> On Tue, 21 Nov 2017 10:33:17 -0500
> joe.korty@concurrent-rt.com wrote:
>
> > On Tue, Nov 21, 2017 at 09:33:52AM -0500, joe.korty@concurrent-rt.com wrote:
> > > On Mon, Nov 20, 2017 at 11:57:51PM -0500, Steven Rostedt wrote:
> > > > On Mon, 20 Nov 2017 23:02:07 -0500
> > > > Steven Rostedt <rostedt@goodmis.org> wrote:
> > > >
> > > >
> > > > > Ideally, I would like to stay close to what upstream -rt does. Would
> > > > > you be able to backport the 4.11-rt patch?
> > > > >
> > > > > I'm currently working on releasing 4.9-rt and 4.4-rt with the latest
> > > > > backports. I could easily add this one too.
> > > >
> > > > Speaking of which. I just backported this patch to 4.4-rt. Is this what
> > > > you are talking about?
> > >
> > > Yes it is.
> > > Thanks for finding that!
> > > Joe
> >
> > I spoke too fast. You will a variant of my one-liner fix
> > when you backport the 4.11.12-r16 patch:
> >
> > rt-Increase-decrease-the-nr-of-migratory-tasks-when-.patch
> >
> > to 4.9-rt and 4.4-rt. The fix of interest is the introduction of
> >
> > p->nr_cpus_allowed = cpumask_weight(&p->cpus_mask);
> >
> > to migrate_enable_update_cpus_allowed().
>
> You totally confused me here.
>
> Hmm, that patch isn't marked for stable. I'm guessing that it should be
> backported.
>
> Now are you saying your patch still needs to be applied if we backport
> this patch? Or does your patch need to be applied to what I have
> already done?
>
> I want to release 4.4-rt (and 4.9-rt) this week so let me know.
Hi Steve,
Just porting that other patch should do the trick. Or you can just apply
my patch, I know that one works as it has actually been tested.
Joe
prev parent reply other threads:[~2017-11-29 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 19:25 joe.korty
2017-11-17 22:48 ` Steven Rostedt
2017-11-20 16:30 ` joe.korty
2017-11-21 4:02 ` Steven Rostedt
2017-11-21 4:57 ` Steven Rostedt
2017-11-21 14:33 ` joe.korty
2017-11-21 15:33 ` joe.korty
2017-11-29 0:22 ` Steven Rostedt
2017-11-29 14:24 ` joe.korty [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=20171129142448.GA18507@zipoli.concurrent-rt.com \
--to=joe.korty@concurrent-rt.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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
Powered by JetHome