From: Cyrill Gorcunov <gorcunov@gmail.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@linux.intel.com>,
Ingo Molnar <mingo@elte.hu>, Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: [PATCH 10/14] [VOYAGER] x86: make disabling the apics functional instead of a flag
Date: Wed, 15 Apr 2009 18:12:51 +0400 [thread overview]
Message-ID: <20090415141251.GA10433@lenovo> (raw)
In-Reply-To: <1239799869.3371.3.camel@mulgrave.int.hansenpartnership.com>
[James Bottomley - Wed, Apr 15, 2009 at 12:51:09PM +0000]
| On Tue, 2009-04-14 at 21:44 +0400, Cyrill Gorcunov wrote:
| > [Cyrill Gorcunov - Tue, Apr 14, 2009 at 09:09:42PM +0400]
| > ...
| > | | diff --git a/arch/x86/kernel/apic/apic.c b/arch/x86/kernel/apic/apic.c
| > | | index f9e830e..aa96dbe 100644
| > | | --- a/arch/x86/kernel/apic/apic.c
| > | | +++ b/arch/x86/kernel/apic/apic.c
| > | | @@ -1539,6 +1539,9 @@ void __init early_init_lapic_mapping(void)
| > | | */
| > | | void __init init_apic_mappings(void)
| > | | {
| > | | + if (disable_apic)
| > | | + return;
| > | | +
| > |
| > | No, we shouldn't do that without additional
| > | code review (otherwise we will loose mapping for fake apic page).
| > | And I suspect we get NULL deref on reboot procedure
| > | if kernel was compiled _with_ SMP support but APIC disabled
| > | by kernel option. hmm, can't find this reference in LKML.
| > | I was telling Ingo about my suspicious on smp operations
| > | when APIC is disabled by option and we're safe _only_ 'cause
| > | we have fake mapping page reserved. For example call of
| > | smp_send_stop() in kernel/panic.c if kernel was compiled _with_ SMP
| > | support and then APIC disabled by kernel option.
| > |
| > | | if (x2apic) {
| > | | boot_cpu_physical_apicid = read_apic_id();
| > | | return;
| > ...
| >
| > Ah, I found that link -- http://lkml.org/lkml/2009/4/12/139
| > I've promised to take a look, unfortunately out of time now.
| > Maybe a bit later.
|
| Hmm, well, looking at this, I think there are two points
|
| The first is that disable_apic should really mean that: It is a
| dangerous option; there are modern CPUs that can't deliver interrupts
| without apics and if you have one and disable it, there's no way of
| preventing the hang that follows (because you can't even get timer
| interrupts).
Even having APIC (local or discrete) cpu (well, not cpu itself but
chipset logic rather) is to provide backward compatibility via 8259(a)
(or familiar one) controller for ExtInt or VirtualWire modes I believe.
Though to be fair I don't have most modern cpus like Core i7 under the
hands to check this. We're talking about x86 family right?
|
| Secondly, I can fix your original emailed problem by having a check for
| disable_apic in the shutdown path on disable_local_apic() ... I think
| that fixes everything?
Yes, it should do the trick. Though there could be other ways
to hang on SMP+APIC compiled kernel with disable_apic passed
I guess :) But testing should reveal the screwed pathes.
|
| James
|
|
Cyrill
next prev parent reply other threads:[~2009-04-15 14:13 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 15:51 [PATCH 00/14] convert voyager over to the x86 quirks model James Bottomley
2009-04-14 15:51 ` [PATCH 01/14] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops James Bottomley
2009-04-14 15:51 ` [PATCH 02/14] [VOYAGER] x86/mca: make mca_nmi_hook external James Bottomley
2009-04-14 15:51 ` [PATCH 03/14] [VOYAGER] x86: add prefill_possible_map to x86_quirks James Bottomley
2009-04-14 15:51 ` [PATCH 04/14] [VOYAGER] x86: use boot_cpu_id instead of zero for checking boot processor James Bottomley
2009-04-14 15:51 ` [PATCH 05/14] [VOYAGER] x86/voyager: Move voyager detection to a new bootparam area James Bottomley
2009-04-14 15:51 ` [PATCH 06/14] [VOYAGER] x86: eliminate subarchitecture file setup_arch.h James Bottomley
2009-04-14 15:51 ` [PATCH 07/14] [VOYAGER] x86: eliminate subarchitecture file entry_arch.h James Bottomley
2009-04-14 15:51 ` [PATCH 08/14] [VOYAGER] x86: eliminate subarchitecture file do_timer.h James Bottomley
2009-04-14 15:51 ` [PATCH 09/14] [VOYAGER] x86: redo irq2 cascade setup James Bottomley
2009-04-14 15:51 ` [PATCH 10/14] [VOYAGER] x86: make disabling the apics functional instead of a flag James Bottomley
2009-04-14 15:51 ` [PATCH 11/14] [VOYAGER] x86/Voyager: add missing QIC call function single gate James Bottomley
2009-04-14 15:51 ` [PATCH 12/14] [VOYAGER] x86/Voyager: replace inline io area reads with readX accessors James Bottomley
2009-04-14 15:51 ` [PATCH 13/14] [VOYAGER] x86/voyager: remove direct use of pg0 in favour of early_ioremap() James Bottomley
2009-04-14 15:51 ` [PATCH 14/14] [VOYAGER] x86/Voyager: Plumb voyager back into the build James Bottomley
2009-04-14 17:09 ` [PATCH 10/14] [VOYAGER] x86: make disabling the apics functional instead of a flag Cyrill Gorcunov
2009-04-14 17:44 ` Cyrill Gorcunov
2009-04-15 12:51 ` James Bottomley
2009-04-15 14:12 ` Cyrill Gorcunov [this message]
2009-04-14 16:31 ` [PATCH 01/14] [VOYAGER] x86: add {safe,hard}_smp_processor_id to smp_ops Cyrill Gorcunov
2009-04-14 16:54 ` James Bottomley
2009-04-14 16:35 ` Jeremy Fitzhardinge
2009-04-14 16:57 ` James Bottomley
2009-04-14 16:27 ` [PATCH 00/14] convert voyager over to the x86 quirks model Joe Perches
2009-04-14 16:57 ` Ingo Molnar
2009-04-14 18:08 ` Ingo Molnar
2009-04-14 23:12 ` James Bottomley
2009-04-15 15:35 ` Ingo Molnar
2009-04-16 21:06 ` James Bottomley
2009-04-16 20:54 ` Jeff Garzik
2009-04-19 23:35 ` Ingo Molnar
2009-04-19 23:54 ` Jeff Garzik
2009-04-20 0:38 ` Ingo Molnar
2009-04-20 16:59 ` James Bottomley
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=20090415141251.GA10433@lenovo \
--to=gorcunov@gmail.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.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