From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Brian Gerst <brgerst@gmail.com>, Tejun Heo <htejun@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: unified percpu stuff
Date: Mon, 26 Jan 2009 17:12:22 -0800 [thread overview]
Message-ID: <497E5F76.10301@goop.org> (raw)
I'm really pleased to see the unified percpu stuff in the kernel, but
unfortunately its breaking Xen at the moment.
It looks like this is just a matter of initializing %gs properly in
xen_start_kernel. Is there any problem with me doing a load_gs_base(0)
somewhere early in xen_start_kernel (arch/x86/xen/enlighten.c)? Is the
initial percpu are and offset for cpu0 all set up? Do I need to make it
#ifdef CONFIG_SMP?
Do I need to do anything for 32-bit? (I haven't tested that yet.)
Thanks,
J
next reply other threads:[~2009-01-27 1:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 1:12 Jeremy Fitzhardinge [this message]
2009-01-27 4:17 ` unified percpu stuff Tejun Heo
2009-01-29 10:43 ` Jeremy Fitzhardinge
2009-01-29 11:01 ` Tejun Heo
2009-01-29 13:43 ` [PATCH] x86: pass in cpu number to switch_to_new_gdt() Brian Gerst
2009-01-29 21:36 ` Jeremy Fitzhardinge
2009-01-29 21:36 ` [PATCH 1/2] x86: split loading percpu segments from loading gdt Jeremy Fitzhardinge
2009-01-29 21:36 ` [PATCH 2/2] xen: setup percpu data pointers Jeremy Fitzhardinge
2009-01-30 8:50 ` Tejun Heo
2009-01-30 8:50 ` [PATCH] x86: pass in cpu number to switch_to_new_gdt() Tejun Heo
2009-01-27 5:57 ` unified percpu stuff Brian Gerst
2009-01-27 7:24 ` Jeremy Fitzhardinge
2009-01-27 12:35 ` Brian Gerst
2009-01-27 17:50 ` Jeremy Fitzhardinge
2009-01-27 19:07 ` Brian Gerst
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=497E5F76.10301@goop.org \
--to=jeremy@goop.org \
--cc=brgerst@gmail.com \
--cc=htejun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.