LKML Archive on
help / color / mirror / Atom feed
From: "Yinghai Lu" <>
To: "Andi Kleen" <>
Cc: "Ingo Molnar" <>,
	"Andrew Morton" <>,
	"Thomas Gleixner" <>,
	"H. Peter Anvin" <>,
	"Linux Kernel Mailing List" <>
Subject: Re: [PATCH] x86_64: show apicid for cpu in proc
Date: Thu, 6 Mar 2008 11:23:09 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 06 Mar 2008 12:41:46 +0100, Andi Kleen <> wrote:
> "Yinghai Lu" <> writes:
>  >                          cpus_weight(per_cpu(cpu_core_map, cpu)));
>  >               seq_printf(m, "core id\t\t: %d\n", c->cpu_core_id);
>  >               seq_printf(m, "cpu cores\t: %d\n", c->booted_cores);
> > +             seq_printf(m, "apicid\t: %02x\n", c->apicid);
>  Seems a little redundant with the boot log, but ok.
>  But it's unclear to the user which apic ID is meant by that. There are
>  two different ones. The one in the LAPIC mapping and the one reported by
>  CPUID. They are not necessarily the same. I think you should clarify that
>  by renaming the field or perhaps report both.

report the apicid and initial apicid at the same time?

but in current code, we didn't use the initial apicid...., actually
initial apic id is more better to get the responding to node/core.

will look at it.


      reply	other threads:[~2008-03-06 19:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-06  9:13 Yinghai Lu
2008-03-06 10:21 ` Ingo Molnar
2008-03-06 11:41 ` Andi Kleen
2008-03-06 19:23   ` Yinghai Lu [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH] x86_64: show apicid for cpu in proc' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).