From: Nathan Lynch <ntl@pobox.com>
To: Zwane Mwaikambo <zwane@arm.linux.org.uk>
Cc: lkml <linux-kernel@vger.kernel.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6-bk: cpu hotplug + preempt = smp_processor_id warnings galore
Date: Tue, 15 Feb 2005 11:26:34 -0600 [thread overview]
Message-ID: <20050215172634.GB22304@otto> (raw)
In-Reply-To: <Pine.LNX.4.61.0502150828520.26742@montezuma.fsmlabs.com>
On Tue, Feb 15, 2005 at 08:29:33AM -0700, Zwane Mwaikambo wrote:
> On Mon, 14 Feb 2005, Nathan Lynch wrote:
>
> > It looks as if we need to explicitly bind worker threads to a newly
> > onlined cpu. This gets rid of the smp_processor_id warnings from
> > cache_reap. Adding a little more instrumentation to the debug
> > smp_processor_id showed that new worker threads were actually running
> > on the wrong cpu...
> >
> > Does this look ok?
>
> Yeah, does that patch suffice for all the warnings?
Nope, ksoftirqd still requires your patch in order to kill the
warnings there.
Nathan
prev parent reply other threads:[~2005-02-15 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-11 23:28 2.6-bk: cpu hotplug + preempt = smp_processor_id warnings galore Nathan Lynch
2005-02-11 23:56 ` Matthias-Christian Ott
2005-02-12 0:56 ` Nathan Lynch
2005-02-12 18:59 ` Zwane Mwaikambo
2005-02-14 21:59 ` Nathan Lynch
2005-02-15 7:02 ` Ingo Molnar
2005-02-16 2:06 ` [PATCH] kthread_bind new worker threads when onlining cpu Nathan Lynch
2005-02-16 5:31 ` [PATCH] Run softirqs on proper processor on offline Zwane Mwaikambo
2005-02-16 5:34 ` Ingo Molnar
2005-02-16 5:51 ` Andrew Morton
2005-02-16 6:17 ` Zwane Mwaikambo
2005-02-15 15:29 ` 2.6-bk: cpu hotplug + preempt = smp_processor_id warnings galore Zwane Mwaikambo
2005-02-15 17:26 ` Nathan Lynch [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=20050215172634.GB22304@otto \
--to=ntl@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=zwane@arm.linux.org.uk \
/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