From: Yinghai Lu <yhlu.kernel@gmail.com>
To: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
Cc: x86@kernel.org, tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86: print real IOAPIC version for x86-64
Date: Wed, 27 May 2009 10:15:02 -0700 [thread overview]
Message-ID: <86802c440905271015l15d46ef8w64558e455120d2a9@mail.gmail.com> (raw)
In-Reply-To: <20090416014230.4885.94926.sendpatchset@localhost.localdomain>
On Tue, May 26, 2009 at 2:48 PM, Naga Chumbalkar
<nagananda.chumbalkar@hp.com> wrote:
> Fix the fact that the IOAPIC version number in the x86_64 code path always
> gets assigned to 0, instead of the correct value.
>
> Before the patch: (from "dmesg" output):
> ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 8, version 0, address 0xfec00000, GSI 0-23 <---
>
> After the patch:
> ACPI: IOAPIC (id[0x08] address[0xfec00000] gsi_base[0])
> IOAPIC[0]: apic_id 8, version 32, address 0xfec00000, GSI 0-23 <---
>
> History:
> io_apic_get_version() was compiled out of the x86_64 code path in the commit
> f2c2cca3acef8b253a36381d9b469ad4fb08563a:
>
> *************************
> Author: Andi Kleen <ak@suse.de>
> Date: Tue Sep 26 10:52:37 2006 +0200
>
> [PATCH] Remove APIC version/cpu capability mpparse checking/printing
>
> ACPI went to great trouble to get the APIC version and CPU capabilities
> of different CPUs before passing them to the mpparser. But all
> that data was used was to print it out. Actually it even faked some data
> based on the boot cpu, not on the actual CPU being booted.
>
> Remove all this code because it's not needed.
>
> Cc: len.brown@intel.com
>
> Signed-off-by: Andi Kleen <ak@suse.de>
> *************************
>
> At the time, the IOAPIC version number was deliberately not printed in the
> x86_64 code path. However, after the x86 and x86_64 files were merged, the net
> result is that the IOAPIC version is printed incorrectly in the x86_64 code
> path.
>
> The patch below provides a fix. I have tested it with acpi, and with acpi=off,
> and did not see any problems.
>
> Signed-off-by: Naga Chumbalkar <nagananda.chumbalkar@hp.com>
> Cc: Yinghai Lu <yhlu.kernel@gmail.com>
Acked-by: Yinghai Lu <yinghai@kernel.org>
next prev parent reply other threads:[~2009-05-27 17:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 21:48 Naga Chumbalkar
2009-05-27 17:15 ` Yinghai Lu [this message]
2009-06-02 0:12 ` [tip:irq/numa] x86: Print " tip-bot for Naga Chumbalkar
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=86802c440905271015l15d46ef8w64558e455120d2a9@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nagananda.chumbalkar@hp.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®