From: Ingo Molnar <mingo@elte.hu>
To: Jan Beulich <jbeulich@novell.com>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org
Subject: Re: x86: meaning of nolapic command line option
Date: Sun, 11 Jan 2009 03:46:42 +0100 [thread overview]
Message-ID: <20090111024642.GA7077@elte.hu> (raw)
In-Reply-To: <496790D1.76E4.0078.0@novell.com>
* Jan Beulich <jbeulich@novell.com> wrote:
> Shouldn't that option imply that all APIC related activity, including
> that relating to IO-APICs or PCI MSI, should be circumvented? I'm
> finding that MSI must be disabled separately, and while most of the
> IO-APIC stuff is indeed not happening, acpi_get_override_irq() only
> checks skip_ioapic_setup, but that doesn't normally set without the
> noapic command line option.
>
> Is there any reason pci_no_msi() and disable_ioapic_setup() shouldn't be
> called when !cpu_has_apic at the end of identify_cpu()?
Yes, both depend on a lapic and they might limp on with whatever the BIOS
gave us, you are right that it should be disabled explicitly. Mind sending
a patch?
Ingo
next prev parent reply other threads:[~2009-01-11 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-09 17:00 x86: meaning of nolapic command line option Jan Beulich
2009-01-11 2:46 ` Ingo Molnar [this message]
2009-01-13 8:19 ` Jan Beulich
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=20090111024642.GA7077@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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