From: "Martin J. Bligh" <mbligh@aracnet.com>
To: Ion Badulescu <ionut@badula.org>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Mikael Pettersson <mikpe@user.it.uu.se>,
Rusty Russell <rusty@rustcorp.com.au>,
linux-kernel@vger.kernel.org, mingo@redhat.com
Subject: Re: [BUG] 2.5.63: ESR killed my box!
Date: Wed, 26 Feb 2003 17:33:37 -0800 [thread overview]
Message-ID: <12910000.1046309616@[10.10.2.4]> (raw)
In-Reply-To: <Pine.LNX.4.44.0302262008280.6844-100000@moisil.badula.org>
> No, look further down in apic.c: APIC_init_uniprocessor() calls
> setup_IO_APIC() which then calls setup_ioapic_ids_from_mpc(). This
> happens after the code quoted above runs.
OK, sounds good - I might be twisting it with the SMP code, which I'm much
more familiar with.
>> boot_cpu_physical_apicid = hard_smp_processor_id();
>> phys_cpu_present_map = 1 << boot_cpu_physical_apicid;
>
> But is it necessarily true that hard_smp_processor_id() equals the APIC
> id?
Well it should be. Except that someone did this for some odd reason
#define hard_smp_processor_id() 0
on non-SMP rather than non-local-apic.
But we could just substitute the real code:
static __inline int hard_smp_processor_id(void)
{
/* we don't want to mark this access volatile - bad code generation
*/
return GET_APIC_ID(*(unsigned long *)(APIC_BASE+APIC_ID));
}
which is in smp.h, but wrapped in #ifdef CONFIG_X86_LOCAL_APIC.
All very twisted. Probably not worth it.
> and that's just about as good as it gets, certainly the CPU knows best
> what its APIC id is.
Absolutely ;-)
M.
next prev parent reply other threads:[~2003-02-27 1:23 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 4:33 Rusty Russell
2003-02-26 5:51 ` Martin J. Bligh
2003-02-26 7:14 ` Rusty Russell
2003-02-26 7:27 ` William Lee Irwin III
2003-02-26 15:20 ` Linus Torvalds
2003-02-26 15:52 ` Martin J. Bligh
2003-02-26 16:37 ` Linus Torvalds
2003-02-26 16:52 ` Martin J. Bligh
2003-02-27 0:32 ` James Cleverdon
2003-02-27 11:11 ` Maciej W. Rozycki
2003-02-26 20:47 ` Ion Badulescu
2003-02-26 21:03 ` Martin J. Bligh
2003-02-26 21:16 ` Ion Badulescu
2003-02-26 21:23 ` Martin J. Bligh
2003-02-26 21:30 ` Linus Torvalds
2003-02-26 21:44 ` Ion Badulescu
2003-02-26 22:05 ` Linus Torvalds
2003-02-26 22:51 ` Martin J. Bligh
2003-02-26 23:07 ` Mikael Pettersson
2003-02-27 0:00 ` Linus Torvalds
2003-02-27 0:45 ` Martin J. Bligh
2003-02-27 1:20 ` Ion Badulescu
2003-02-27 1:33 ` Martin J. Bligh [this message]
2003-02-27 10:33 ` Mikael Pettersson
2003-02-27 1:26 ` Ion Badulescu
2003-02-27 1:40 ` Martin J. Bligh
2003-02-27 7:17 ` Rusty Russell
2003-02-26 8:43 Rusty Russell
2003-02-26 22:34 Grover, Andrew
2003-03-01 1:42 Mallick, Asit K
2003-03-01 3:07 Mallick, Asit K
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='12910000.1046309616@[10.10.2.4]' \
--to=mbligh@aracnet.com \
--cc=ionut@badula.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
--cc=mingo@redhat.com \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@transmeta.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
all inboxes | Powered by JetHome®