mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: tglx@linutronix.de
Cc: linux-kernel@vger.kernel.org
Subject: The difference between x86_cpu_to_apicid and x86_bios_cpu_apicid
Date: Sat, 18 Jun 2016 16:24:22 +0800	[thread overview]
Message-ID: <20160618082422.GA4065@x1.redhat.com> (raw)

Hi Thomas,

Sorry to bother you. I am always wondering what's the difference between
x86_cpu_to_apicid and x86_bios_cpu_apicid. Or in other words, I don't
know why x86_bios_cpu_apicid is required. From code both
x86_cpu_to_apicid and x86_bios_cpu_apicid stores the apicid correspond
to a certain logic cpu number. With my understanding x86_cpu_to_apicid
can do what x86_bios_cpu_apicid is doing except for its usage in below
commit.

commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
Author: Thomas Gleixner <tglx@linutronix.de>
Date:   Mon Feb 22 22:19:15 2016 +0000

    x86/topology: Create logical package id

Could you please help to explain when it's convenient to you?

Thanks
Baoquan

                 reply	other threads:[~2016-06-18  8:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20160618082422.GA4065@x1.redhat.com \
    --to=bhe@redhat.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
Powered by JetHome