From: ebiederm@xmission.com (Eric W. Biederman)
To: "Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com>
Cc: <vgoyal@in.ibm.com>, "Andrew Morton" <akpm@osdl.org>,
<fastboot@osdl.org>, <linux-kernel@vger.kernel.org>,
"Andi Kleen" <ak@suse.de>,
"Zwane Mwaikambo" <zwane@arm.linux.org.uk>,
"Brown, Len" <len.brown@intel.com>
Subject: Re: [Fastboot] [PATCH] i386: move apic init in init_IRQs
Date: Mon, 31 Oct 2005 11:18:56 -0700 [thread overview]
Message-ID: <m1fyqha6sv.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <19D0D50E9B1D0A40A9F0323DBFA04ACCE04DFF@USRV-EXCH4.na.uis.unisys.com> (Natalie Protasevich's message of "Mon, 31 Oct 2005 11:04:52 -0600")
"Protasevich, Natalie" <Natalie.Protasevich@UNISYS.com> writes:
> Hi Eric,
>
> There is another problem with that patch - it broke ES7000, I kept
> getting timer panics. It turned out that check_timer() runs before the
> actual APIC destination is set up. The IO-APIC uses
> cpu_to_logical_apicid to find the destination - which needs
> cpu_2_logical_apicid[] to be filled - which only happens after
> processors are booted. At the time when check_timer() runs, it will
> always be BAD_APICID (0xFF - broadcast) as the IO-APIC rte destination
> for the timer, but ES7000 hardware happened not to support 0xFF so it
> panics. I used bios_cpu_apicid[] to bring it up, but
> cpu_to_logical_apicid is the only one that is kept up-to-date in the
> hotplug case, so I cannot replace it in the cpu_mask_to_apicid().
>
> There are probably some ways to fix this such as one below that I tried
> (in mpparse.c):
>
> if (m->mpc_cpuflag & CPU_BOOTPROCESSOR) {
> Dprintk(" Bootup CPU\n");
> boot_cpu_physical_apicid = m->mpc_apicid;
> + cpu_2_logical_apicid[num_processors] = m->mpc_apicid;
> }
> it worked, but looks more like a kludge of course. I think IO-APIC
> setup has to happen after processors were brought online and so is
> check_timer(), if timer is connected through the IO-APIC.
The first cpu is brought online much earlier than the rest. So
we just need to setup a table for boot cpu earlier. From the looks
of it mach-es700 won't work if you compile a uniprocessor kernel
for it right now.
We need to do this a little later than in mptable but this should be a fairly
simple one or two line change.
If people keep breaking the subarchitectures by accident we might even
inspire someone to make a comprehensible sub architecture implentation
on x86 one of these days.
Eric
next prev parent reply other threads:[~2005-10-31 18:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 17:04 Protasevich, Natalie
2005-10-31 17:18 ` Zwane Mwaikambo
2005-10-31 17:30 ` Eric W. Biederman
2005-10-31 20:26 ` Zwane Mwaikambo
2005-10-31 18:18 ` Eric W. Biederman [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-31 18:31 Protasevich, Natalie
2005-11-01 7:41 ` Eric W. Biederman
2005-10-04 15:04 Eric W. Biederman
2005-10-21 13:33 ` [Fastboot] " Vivek Goyal
2005-10-21 14:45 ` Eric W. Biederman
2005-10-21 16:53 ` Albert Herranz
2005-10-21 18:01 ` Eric W. Biederman
2005-10-22 14:52 ` Vivek Goyal
2005-10-22 15:23 ` Eric W. Biederman
2005-10-24 13:03 ` Vivek Goyal
2005-10-24 15:36 ` Eric W. Biederman
2005-10-25 7:17 ` Eric W. Biederman
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=m1fyqha6sv.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Natalie.Protasevich@UNISYS.com \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=fastboot@osdl.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
--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
all inboxes | Powered by JetHome®