public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Siddha, Suresh B" <suresh.b.siddha@intel.com>
To: Andi Kleen <ak@suse.de>
Cc: Martin Wilck <martin.wilck@fujitsu-siemens.com>,
	linux-kernel@vger.kernel.org
Subject: Re: APIC version and 8-bit APIC IDs
Date: Fri, 12 Aug 2005 11:19:16 -0700	[thread overview]
Message-ID: <20050812111916.A15541@unix-os.sc.intel.com> (raw)
In-Reply-To: <20050812145725.GD922@wotan.suse.de>; from ak@suse.de on Fri, Aug 12, 2005 at 04:57:25PM +0200

On Fri, Aug 12, 2005 at 04:57:25PM +0200, Andi Kleen wrote:
> On Fri, Aug 12, 2005 at 04:55:40PM +0200, Martin Wilck wrote:
> > I wrote:
> > 
> > >>How so? The XAPIC version check should work there.
> > >
> > >ACPI: LAPIC (acpi_id[0x11] lapic_id[0x21] enabled)
> > >Processor #33 15:4 APIC version 16
> > >ACPI: LAPIC (acpi_id[0x12] lapic_id[0x26] enabled)
> > >Processor #38 15:4 APIC version 16
> > 
> > Forget it. I have fallen prey to  this line:
> > 
> > 	processor.mpc_apicver = 0x10; /* TBD: lapic version */
> > 
> > in arch/x86_64/kernel/mpparse.c.
> > I am used to get correct answers from Linux :-)
> 
> Heh. Should probably fix that. Can you file a bug with the ACPI
> people on http://bugzilla.kernel.org ? (or do a patch?)

Here is the patch.

--
Fix the apic version that gets printed during boot. 

Signed-off-by: Suresh Siddha <suresh.b.siddha@intel.com>

--- linux-2.6.13-rc6/arch/x86_64/kernel/mpparse.c~	2005-08-12 10:19:07.037696416 -0700
+++ linux-2.6.13-rc6/arch/x86_64/kernel/mpparse.c	2005-08-12 10:19:38.098974384 -0700
@@ -707,7 +707,7 @@
 
 	processor.mpc_type = MP_PROCESSOR;
 	processor.mpc_apicid = id;
-	processor.mpc_apicver = 0x10; /* TBD: lapic version */
+	processor.mpc_apicver = GET_APIC_VERSION(apic_read(APIC_LVR));
 	processor.mpc_cpuflag = (enabled ? CPU_ENABLED : 0);
 	processor.mpc_cpuflag |= (boot_cpu ? CPU_BOOTPROCESSOR : 0);
 	processor.mpc_cpufeature = (boot_cpu_data.x86 << 8) | 

  parent reply	other threads:[~2005-08-12 18:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42FC8461.2040102@fujitsu-siemens.com.suse.lists.linux.kernel>
2005-08-12 11:43 ` APIC version and 8-bit APIC IDs Andi Kleen
2005-08-12 13:21   ` Martin Wilck
2005-08-12 13:32     ` Andi Kleen
2005-08-12 13:51       ` Martin Wilck
2005-08-12 14:55         ` Martin Wilck
2005-08-12 14:57           ` Andi Kleen
2005-08-12 16:37             ` yhlu
2005-08-12 16:42               ` Andi Kleen
2005-08-12 17:44                 ` yhlu
2005-08-22  9:50                   ` Martin Wilck
2005-08-23 11:10                     ` Maciej W. Rozycki
2005-08-26 14:01                       ` Martin Wilck
2005-08-26 14:50                         ` Maciej W. Rozycki
2005-08-29  7:25                           ` Martin Wilck
2005-08-12 18:19             ` Siddha, Suresh B [this message]
2005-08-12 18:22               ` Andi Kleen
2005-08-12 18:40                 ` Siddha, Suresh B
2005-08-12 18:50                   ` Andi Kleen
2005-08-31 13:13   ` Martin Wilck
2005-08-31 13:25     ` Maciej W. Rozycki
2005-08-31 14:27       ` Martin Wilck
     [not found]       ` <4315B2D9.6080700@fujitsu-siemens.com>
     [not found]         ` <Pine.LNX.4.61L.0508311450020.10940@blysk.ds.pg.gda.pl>
2005-08-31 14:50           ` Martin Wilck
2005-08-31 14:40     ` Andi Kleen
2005-08-12 11:13 Martin Wilck

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=20050812111916.A15541@unix-os.sc.intel.com \
    --to=suresh.b.siddha@intel.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.wilck@fujitsu-siemens.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