mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Randy.Dunlap" <rdunlap@xenotime.net>
To: Patrizio Bassi <patrizio.bassi@gmail.com>
Cc: "Randy.Dunlap" <rdunlap@xenotime.net>,
	"Kernel," <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26 vanilla paravirt config issue
Date: Thu, 24 Jul 2008 10:51:25 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0807241047290.3283@shark.he.net> (raw)
In-Reply-To: <742b1fb30807241045q21592679xe32f59b7ab77be21@mail.gmail.com>

On Thu, 24 Jul 2008, Patrizio Bassi wrote:

> 2008/7/24 Randy.Dunlap <rdunlap@xenotime.net>:
> >
> > On Thu, 24 Jul 2008, Patrizio Bassi wrote:
> >
> > > Hi All
> > >
> > > on my amd64 profile i cannot disable PARAVIRT option.
> > >
> > > even if i disable all i still get in my .config:
> > >
> > > # CONFIG_X86_ES7000 is not set
> > > # CONFIG_X86_RDC321X is not set
> > > CONFIG_X86_VSMP=y
> > > # CONFIG_PARAVIRT_GUEST is not set
> > > CONFIG_PARAVIRT=y    <<<<-------------------------------- issue
> > > # CONFIG_MEMTEST_BOOTPARAM is not set
> > > # CONFIG_M386 is not set
> > >
> > > how to disable it? i guess it's a config bug.
> >
> > Nope.  You have CONFIG_X86_VSMP enabled, which selects PARAVIRT:
> >
> > config X86_VSMP
> >        bool "Support for ScaleMP vSMP"
> >        select PARAVIRT
> >        depends on X86_64
> >
> > > CC me i'm not subscribed.
> 
> Oh thanks, so this means ScaleMP support can be enabled only with paravirt?

Yes.

> At the moment i don't understand the need, maybe i should study some
> documentation, do you have any pointer?

No, I don't recall seeing any docs for it.
You could try www.scalemp.com .

-- 
~Randy

  parent reply	other threads:[~2008-07-24 17:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 17:15 Patrizio Bassi
2008-07-24 17:41 ` Randy.Dunlap
     [not found]   ` <742b1fb30807241045q21592679xe32f59b7ab77be21@mail.gmail.com>
2008-07-24 17:51     ` Randy.Dunlap [this message]
2008-07-24 18:30 ` 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=Pine.LNX.4.64.0807241047290.3283@shark.he.net \
    --to=rdunlap@xenotime.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patrizio.bassi@gmail.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

all inboxes | Powered by JetHome®