public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Ingo Molnar <mingo@kernel.org>
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 12:40:56 -0400	[thread overview]
Message-ID: <551ACE18.4070501@oracle.com> (raw)
In-Reply-To: <20150331155549.GA30951@gmail.com>

On 03/31/2015 11:55 AM, Ingo Molnar wrote:
>
> * 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
>


Yes, I was somewhat out-of-date, sorry. Let me re-test this and submit v2.

-boris

      reply	other threads:[~2015-03-31 16:42 UTC|newest]

Thread overview: 3+ 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
2015-03-31 16:40   ` Boris Ostrovsky [this message]

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=551ACE18.4070501@oracle.com \
    --to=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@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox