From: Ben Collins <ben.collins@ubuntu.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
Nathan Lynch <ntl@pobox.com>,
linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] fix workqueue oops during cpu offline
Date: Thu, 05 Jan 2006 09:30:23 -0500 [thread overview]
Message-ID: <1136471423.4430.58.camel@grayson> (raw)
In-Reply-To: <1136440988.4840.60.camel@localhost.localdomain>
On Thu, 2006-01-05 at 17:03 +1100, Benjamin Herrenschmidt wrote:
> On Thu, 2006-01-05 at 15:58 +1000, Nigel Cunningham wrote:
> > Hi.
> >
> > On Thursday 05 January 2006 14:58, Nathan Lynch wrote:
> > > With 2.6.15, powerpc systems oops when cpu 0 is offlined. This is a
> > > regression from 2.6.14, caused by commit id
> > > bce61dd49d6ba7799be2de17c772e4c701558f14 ("Fix hardcoded cpu=0 in
> > > workqueue for per_cpu_ptr() calls").
> >
> > So it's valid on ppc for cpu 0 to be taken offline? IIRC, trying that on my P4
> > a while back did nothing. I think you'll find other places that assume that
> > cpu 0 is always up (swsusp? ... I should check suspend2).
>
> It's bogus, cpu0 can be put offline.
Not only that, but on some systems it may never even exist. Which was
the whole reason for my problem in the first place with the workqueue
code.
I haven't tested it, but the patch would appear to work for me. Since
sparc64 doesn't support CPU hotplug, the cpu_possible_map is just a copy
of cpu_present_map. I'll merge it into my tree and give it a run on the
ultra3k.
--
Ben Collins <ben.collins@ubuntu.com>
Developer
Ubuntu Linux
next prev parent reply other threads:[~2006-01-05 14:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 4:58 [PATCH] fix workqueue oops during cpu offline Nathan Lynch
2006-01-05 5:58 ` Nigel Cunningham
2006-01-05 6:03 ` Benjamin Herrenschmidt
2006-01-05 14:30 ` Ben Collins [this message]
2006-01-05 21:45 ` Tony Luck
2006-01-05 22:42 ` Ashok Raj
2006-01-05 23:18 ` Nathan Lynch
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=1136471423.4430.58.camel@grayson \
--to=ben.collins@ubuntu.com \
--cc=akpm@osdl.org \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@cyclades.com \
--cc=ntl@pobox.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