All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark Langsdorf" <mark.langsdorf@amd.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: dom0 and apicid not equal to cpuid
Date: Thu, 14 Feb 2008 16:16:39 -0600	[thread overview]
Message-ID: <200802141616.39410.mark.langsdorf@amd.com> (raw)
In-Reply-To: <C3D278A0.13859%Keir.Fraser@cl.cam.ac.uk>

On Friday 08 February 2008, Keir Fraser wrote:
> On 8/2/08 21:19, "Keir Fraser" <Keir.Fraser@cl.cam.ac.uk> wrote:
> 
> >> I know some of the code needs to be added to mpparse-xen.c,
> >> but it looks like the relevant code was #ifdef'd out in
> >> the first place.  Does anyone know why the code to match
> >> cpuids to apicids was removed and what would need to be
> >> done to restore it?
> > 
> > Probably most of the things that depend on it are actually managed by Xen
> > itself. Possibly this assumption is wrong and the code needs to be re-added,
> > or perhaps the problem is actually within Xen?
> > 
> > Can you point out the specific troubling code in our Linux tree (e.g., the
> > specific #if0'ed code, and also the place where the kernel ultimately gets
> > confused and the request fails)?
> 
> Also, a link to the upstream patch, or area of code in an upstream kernel,
> that you think needs to be added would be useful too.

Simpler solution that the one I proposed above: Fix the APIC to ACPI mappings
in drivers/xen/core/smpboot.c.  That doesn't require pinning vcpus or knowing
about the underlying APIC/ACPI/CPU ID interaction.  

Patch for this solution below:


Xen dom0 arbitrarily assigns APIC ID x to CPU ID x.  Make dom0 also assign
the APIC ID to ACPI ID mapping in the same way.

Signed-off-by: Mark Langsdorf <mark.langsdorf@amd.com>

diff -r 08e85e79c65d drivers/xen/core/smpboot.c
--- a/drivers/xen/core/smpboot.c	Mon Feb 11 11:05:27 2008 +0000
+++ b/drivers/xen/core/smpboot.c	Thu Feb 14 16:12:41 2008 -0600
@@ -269,6 +269,7 @@ void __init smp_prepare_cpus(unsigned in
 
 	cpu_2_logical_apicid[0] = 0;
 	x86_cpu_to_apicid[0] = 0;
+	x86_acpiid_to_apicid[0] = 0;
 
 	current_thread_info()->cpu = 0;
 
@@ -317,6 +318,7 @@ void __init smp_prepare_cpus(unsigned in
 
 		cpu_2_logical_apicid[cpu] = cpu;
 		x86_cpu_to_apicid[cpu] = cpu;
+		x86_acpiid_to_apicid[cpu] = cpu;
 
 		idle = fork_idle(cpu);
 		if (IS_ERR(idle))

  reply	other threads:[~2008-02-14 22:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-08 21:05 dom0 and apicid not equal to cpuid Langsdorf, Mark
2008-02-08 21:19 ` Keir Fraser
2008-02-08 21:22   ` Keir Fraser
2008-02-14 22:16     ` Mark Langsdorf [this message]
2008-02-14 22:22       ` Keir Fraser
2008-02-11 22:38   ` Langsdorf, Mark
2008-02-11 23:08     ` Keir Fraser
2008-02-12 10:29     ` Keir Fraser
2008-02-12 15:33       ` Langsdorf, Mark
2008-02-12 16:43         ` Keir Fraser
2008-02-12 19:09           ` Langsdorf, Mark
2008-02-13  9:23             ` Jan Beulich
2008-02-13 10:07               ` Keir Fraser
2008-02-13 10:04             ` Keir Fraser
2008-02-13 22:52               ` Mark Langsdorf
2008-02-14  8:26                 ` Keir Fraser

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=200802141616.39410.mark.langsdorf@amd.com \
    --to=mark.langsdorf@amd.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.