From: Grant Grundler <grundler@parisc-linux.org>
To: Randolph Chung <randolph@tausq.org>
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Spinlock patch, take 2
Date: Wed, 24 Mar 2004 23:00:40 -0700 [thread overview]
Message-ID: <20040325060040.GA9159@colo.lackof.org> (raw)
In-Reply-To: <20040325072831.GT750@tausq.org>
On Wed, Mar 24, 2004 at 11:28:31PM -0800, Randolph Chung wrote:
> I think this is correct, but i'm not sure. i believe this is part of
> the hotplug cpu patches that are being disucssed and we are waiting for
> that to do more smp work.
>
> jejb/willy, any comments on this?
I just started looking at this.
We don't need cpu_present_map.
We should use cpu_possible_mask in our arch/parisck/kernel/smp.c.
grant
prev parent reply other threads:[~2004-03-25 6:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-15 6:33 [parisc-linux] Spinlock patch, take 2 Randolph Chung
2004-03-15 7:37 ` Carlos O'Donell
2004-03-15 7:43 ` Randolph Chung
2004-03-19 14:30 ` Joel Soete
2004-03-19 16:27 ` Joel Soete
2004-03-25 7:28 ` Randolph Chung
2004-03-25 6:00 ` Grant Grundler [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=20040325060040.GA9159@colo.lackof.org \
--to=grundler@parisc-linux.org \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.org \
/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