mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Ido Yariv <ido@wizery.com>
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org, shai@scalemp.com,
	tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:x86/platform] x86/vsmp: Use hypervisor layer for initialization
Date: Wed, 22 Aug 2012 12:08:45 +0200	[thread overview]
Message-ID: <20120822100845.GB26323@gmail.com> (raw)
In-Reply-To: <20120822094648.GA14941@WorkStation.localnet>


* Ido Yariv <ido@wizery.com> wrote:

> Hi Ingo,
> 
> On Wed, Aug 22, 2012 at 11:11:41AM +0200, Ingo Molnar wrote:
> > 
> > * tip-bot for Ido Yariv <ido@wizery.com> wrote:
> > 
> > > Commit-ID:  c00679af441c5be76e195deed2c76fef65a5d102
> > > Gitweb:     http://git.kernel.org/tip/c00679af441c5be76e195deed2c76fef65a5d102
> > > Author:     Ido Yariv <ido@wizery.com>
> > > AuthorDate: Wed, 8 Aug 2012 20:01:38 +0300
> > > Committer:  Ingo Molnar <mingo@kernel.org>
> > > CommitDate: Wed, 22 Aug 2012 10:48:05 +0200
> > > 
> > > x86/vsmp: Use hypervisor layer for initialization
> > > 
> > > vSMP detection and initialization could be done by
> > > the hypervisor layer, so set it up that way.
> > > 
> > > This cleans up vSMP initialization.
> > > 
> > > Signed-off-by: Ido Yariv <ido@wizery.com>
> > > Acked-by: Shai Fultheim <shai@scalemp.com>
> > > Link: http://lkml.kernel.org/r/1344445299-22142-1-git-send-email-ido@wizery.com
> > > Signed-off-by: Ingo Molnar <mingo@kernel.org>
> > > ---
> > >  arch/x86/include/asm/hypervisor.h |    1 +
> > >  arch/x86/include/asm/setup.h      |    7 -------
> > >  arch/x86/kernel/cpu/hypervisor.c  |    1 +
> > >  arch/x86/kernel/setup.c           |    2 --
> > >  arch/x86/kernel/vsmp_64.c         |   27 +++++++++++++++++----------
> > >  5 files changed, 19 insertions(+), 19 deletions(-)
> > 
> > I had to zap this commit because it breaks the build:
> > 
> > (.init.rodata+0x4c8): undefined reference to `x86_hyper_vsmp'
> 
> I failed to notice that vsmp_64.c is only built on 64bit, so this will
> break on 32bit builds.
> 
> How about the patch below?

Please test it in the configs that matter and resubmit.

Thanks,

	Ingo

  reply	other threads:[~2012-08-22 10:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 17:01 [PATCH 1/2] vsmp: " Ido Yariv
2012-08-08 17:01 ` [PATCH v2 2/2] x86/pat: Avoid contention on cpa_lock if possible Ido Yariv
2012-08-22  8:47   ` Ingo Molnar
2012-08-22  9:53     ` Ido Yariv
2012-08-22 10:07       ` Ingo Molnar
2012-08-19  9:12 ` [PATCH 1/2] vsmp: Use hypervisor layer for initialization Ido Yariv
2012-08-22  9:04 ` [tip:x86/platform] x86/vsmp: " tip-bot for Ido Yariv
2012-08-22  9:11   ` Ingo Molnar
2012-08-22  9:46     ` Ido Yariv
2012-08-22 10:08       ` Ingo Molnar [this message]
2012-08-22 11:20         ` [PATCH v2] " Ido Yariv
2012-08-22 17:37           ` Ingo Molnar
2012-08-22 17:39             ` Shai Fultheim (Shai@ScaleMP.com)
2012-08-22 17:48               ` Ingo Molnar
2012-08-22 18:07                 ` Shai Fultheim (Shai@ScaleMP.com)
2012-08-22 18:19                   ` Ingo Molnar

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=20120822100845.GB26323@gmail.com \
    --to=mingo@kernel.org \
    --cc=hpa@zytor.com \
    --cc=ido@wizery.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=shai@scalemp.com \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome