public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [PATCH 1/3] xen: setup percpu data pointers
Date: Thu, 05 Feb 2009 15:29:12 +0900	[thread overview]
Message-ID: <498A8738.9050200@gmail.com> (raw)
In-Reply-To: <49876BD3.5070804@goop.org>

Jeremy Fitzhardinge wrote:
> We need to access percpu data fairly early, so set up the percpu
> registers as soon as possible.  We only need to load the appropriate
> segment register.  We already have a GDT, but its hard to change it
> early because we need to manipulate the pagetable to do so, and that
> hasn't been set up yet.
> 
> Also, set the kernel stack when bringing up secondary CPUs.  If we
> don't they all end up sharing the same stack...
> 
> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> ---
> arch/x86/xen/enlighten.c |   16 ++++++++++++++++
> arch/x86/xen/smp.c       |    7 ++++++-
> arch/x86/xen/xen-ops.h   |    2 ++
> 3 files changed, 24 insertions(+), 1 deletion(-)

Applied 1-3 to #tj-percpu with trivial modification on #2 (will reply
to the message).

Thanks.

-- 
tejun

  reply	other threads:[~2009-02-05  6:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 21:55 [PATCH 1/3] xen: setup percpu data pointers Jeremy Fitzhardinge
2009-02-05  6:29 ` Tejun Heo [this message]
2009-02-05  6:49   ` Tejun Heo
2009-02-05  7:17     ` Jeremy Fitzhardinge
2009-02-05 10:30       ` Tejun Heo
2009-02-05 14:57         ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2009-01-31  1:42 Jeremy Fitzhardinge

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=498A8738.9050200@gmail.com \
    --to=htejun@gmail.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox