From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: Arjan van de Ven <arjanv@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: finding out the boot cpu number from userspace
Date: Mon, 2 Aug 2004 10:46:59 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0408021038550.19226@chaos> (raw)
In-Reply-To: <Pine.LNX.4.58.0408021028010.4095@montezuma.fsmlabs.com>
On Mon, 2 Aug 2004, Zwane Mwaikambo wrote:
> On Mon, 2 Aug 2004, Arjan van de Ven wrote:
>
> > assuming cpu 0 is the boot cpu sounds fragile/incorrect, but for irqbalanced
> > I'd like to find out which cpu is the boot cpu, is there a good way of doing
> > so ?
> >
> > The reason for needing this is that some firmware only likes running on the
> > boot cpu so I need to bind firmware-related irq's to that cpu ideally.
>
> How about something like mptable which will give you the BSP flag from the
> MP table? I believe this gropes around /dev/mem.
Once CPUs other than 0 are enabled, they take part in the boot
process. They don't spin forever so I don't understand the notion
of 'boot CPU'.
Also firmware has no clue about what CPU is tickling it. There is no
possible way for it to find out, or even care. If some hardware
engineer claimed differently, he/she/it is pulling your chain (or
needs to learn how busses, CPUs and FPGAs work)! There is a
Virtual Wire specification that guarantees that no firmware
can possibly care.
Cheers,
Dick Johnson
Penguin : Linux version 2.4.26 on an i686 machine (5570.56 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-08-02 14:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-02 12:16 Arjan van de Ven
2004-08-02 13:37 ` Dave Jones
2004-08-02 14:13 ` Alan Cox
2004-08-02 14:30 ` Zwane Mwaikambo
2004-08-02 14:46 ` Richard B. Johnson [this message]
2004-08-02 15:50 ` Martin J. Bligh
2004-08-02 16:58 ` Jeff Moyer
2004-08-02 17:23 ` Martin J. Bligh
2004-08-02 17:42 ` Alan Cox
2004-08-02 18:49 ` Martin J. Bligh
2004-08-02 18:23 ` Alan Cox
2004-08-02 20:08 ` Chris Wedgwood
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=Pine.LNX.4.53.0408021038550.19226@chaos \
--to=root@chaos.analogic.com \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®