All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com,
	konrad.wilk@oracle.com, david.vrabel@citrix.com,
	linux-kernel@vger.kernel.org, xen-devel@lists.xenproject.org,
	luto@amacapital.net
Subject: Re: [PATCH] x86: Factor out common CPU initialization code
Date: Tue, 31 Mar 2015 17:55:50 +0200	[thread overview]
Message-ID: <20150331155549.GA30951@gmail.com> (raw)
In-Reply-To: <1427809518-31433-1-git-send-email-boris.ostrovsky@oracle.com>


* Boris Ostrovsky <boris.ostrovsky@oracle.com> wrote:

> Some of x86 bare-metal and Xen CPU initialization code is common between the two
> and therefore can be factored out to avoid code duplication.
> 
> As a side effect, doing so will also extend the fix provided by commit
> a7fcf28d431e ("x86/asm/entry: Replace this_cpu_sp0() with current_top_of_stack()
> to x86_32") to 32-bit Xen PV guests.
> 
> Signed-off-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
> ---
>  arch/x86/include/asm/smp.h |  1 +
>  arch/x86/kernel/smpboot.c  | 39 +++++++++++++++++++++++----------------
>  arch/x86/xen/smp.c         | 14 +-------------
>  3 files changed, 25 insertions(+), 29 deletions(-)

This does not apply to the latest x86 tree (tip:master).

Thanks,

	Ingo

  reply	other threads:[~2015-03-31 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-31 13:45 [PATCH] x86: Factor out common CPU initialization code Boris Ostrovsky
2015-03-31 15:55 ` Ingo Molnar [this message]
2015-03-31 16:40   ` Boris Ostrovsky
2015-03-31 16:40   ` Boris Ostrovsky
2015-03-31 15:55 ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
2015-03-31 13:45 Boris Ostrovsky

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=20150331155549.GA30951@gmail.com \
    --to=mingo@kernel.org \
    --cc=boris.ostrovsky@oracle.com \
    --cc=david.vrabel@citrix.com \
    --cc=hpa@zytor.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=xen-devel@lists.xenproject.org \
    /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.