From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: "Bryan O'Donoghue" <bryan.odonoghue@linux.intel.com>,
Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: APIC logic bug in kernel
Date: Mon, 30 Apr 2012 01:14:52 +0100 (BST) [thread overview]
Message-ID: <alpine.LFD.2.00.1204300106540.19691@eddie.linux-mips.org> (raw)
In-Reply-To: <4F7B3D93.4030405@linux.intel.com>
Hi Bryan,
Apologies for a late reply, I don't check mailing list traffic regularly.
On Tue, 3 Apr 2012, Bryan O'Donoghue wrote:
> I'm looking at the code in arch/x86/kernel/apic/apic.c specifically the code
> path that checks for x86_vendor == X86_VENDOR_INTEL with boot_cpu_data.x86 =
> 5.
>
> As I understand the code, BIOS will have informed kernel that it has an APIC
> based on mps tables. If the CPU family == 5, the function apic_verify() will
> be called.
>
> Problem is apic_verify() does an rdmsr for an MSR that was not included in IA
> until P6.
>
> Specifically rdmsr/wrmsr instructions in apic.c are not P5 compatible - since
> the MSR IA32_APIC_BASE was not introduced until P6_01 - as listed in the
> system programming guide volume 3.
>
> Are all of these rdmsr/wrmsr calls made with an awareness of P5 ?
>
> Example:
>
> We check in apic_verify() if cpuid(1).edx has bit 9 (local APIC) set.
> If so we set CPU capability FEATURE_APIC and rdmsr/wrmsr to 0x1B
>
> arch/x86/include/asm/msr-index.h:#define MSR_IA32_APICBASE
> 0x0000001b
>
> As I read this code it is perfectly valid for a P5, to have an APIC, report it
> has APIC capability via BIOS and CPUID and then subsequently to go ahead and
> touch the IA32_APIC_BASE MSR.
>
> Basically this code doesn't seem to match the spec, am I missing a trick ?
You mean this piece:
if (!cpu_has_apic) {
[...]
} else {
if (apic_verify())
return -1;
}
in detect_init_APIC(), I presume? Looks like a regression to me, and will
trigger a #GP on RDMSR on Pentium-class processors. Additionally the
messages produced by apic_verify() look bogus to me in this context.
Ingo, can you please look at it or find someone to? Thanks.
Maciej
prev parent reply other threads:[~2012-04-30 0:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-03 18:12 Bryan O'Donoghue
2012-04-30 0:14 ` Maciej W. Rozycki [this message]
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=alpine.LFD.2.00.1204300106540.19691@eddie.linux-mips.org \
--to=macro@linux-mips.org \
--cc=bryan.odonoghue@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
/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
Powered by JetHome