public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: David Miller <davem@davemloft.net>
Cc: javier@guerrag.com, anthony@codemonkey.ws, blauwirbel@gmail.com,
	kvm@vger.kernel.org, sparclinux@vger.kernel.org,
	levon@movementarian.org
Subject: Re: KVM for Sparc?
Date: Tue, 23 Sep 2008 11:07:31 -0500	[thread overview]
Message-ID: <1222186051.3545.13.camel@localhost.localdomain> (raw)
In-Reply-To: <20080922.151500.139839534.davem@davemloft.net>

On Mon, 2008-09-22 at 15:15 -0700, David Miller wrote:
> From: Hollis Blanchard <hollisb@us.ibm.com>
> Date: Mon, 22 Sep 2008 16:27:40 -0500
> 
> > On Mon, 2008-09-22 at 15:31 -0500, Javier Guerra wrote:
> > > On Mon, Sep 22, 2008 at 3:18 PM, Hollis Blanchard <hollisb@us.ibm.com> wrote:
> > > > It would be even more interesting to implement host support on the Sparc
> > > > processors with hardware virtualization support.
> > > 
> > > Does Sparc processors also have 'virtualization support' as an extra
> > > feature? i thought that 'non virtualizationability' was an
> > > intel-specific limitation.  (come on... creating a privileged mode and
> > > not trapping violations? who else would design like that?)
> > 
> > Trapping on privileged instructions is enough to get you virtualization
> > functionality, but for good performance you really want additional
> > hardware support to avoid those traps in the first place.
> 
> That's not really available on sparc.

As far as I can see, you have a hypervisor privilege mode which allows
your guests to execute privileged instructions like WRPR without
trapping.

Without that hardware support (with only 2 privilege levels), you'd be
forced to run the guest kernel in user mode, trapping on every WRPR (for
example). That's what I mean by hardware helping you to avoid traps.

-- 
Hollis Blanchard
IBM Linux Technology Center


  parent reply	other threads:[~2008-09-23 16:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f43fc5580809210538r38a29d8dpc74342a2bceea109@mail.gmail.com>
2008-09-21 12:52 ` KVM for Sparc? Blue Swirl
2008-09-22 19:34   ` Anthony Liguori
2008-09-22 20:18     ` Hollis Blanchard
2008-09-22 20:26       ` David Miller
2008-09-22 21:25         ` Hollis Blanchard
2008-09-22 22:14           ` David Miller
2008-09-23 15:34             ` Blue Swirl
2008-09-23 20:41               ` David Miller
2008-09-24 17:22                 ` Blue Swirl
2008-09-24 19:29                   ` David Miller
2008-09-22 20:31       ` Javier Guerra
2008-09-22 21:02         ` David Miller
2008-09-22 21:27         ` Hollis Blanchard
2008-09-22 22:15           ` David Miller
2008-09-23 15:52             ` Blue Swirl
2008-09-23 16:07             ` Hollis Blanchard [this message]
2008-09-23 20:44               ` David Miller
2008-09-22 20:24     ` David Miller
2008-09-23 15:28       ` Blue Swirl
2008-09-23 20:38         ` David Miller
2008-09-24 17:20           ` Blue Swirl
2008-09-24 18:06             ` Blue Swirl
2008-09-24 19:29               ` David Miller
2008-09-25 16:58                 ` Blue Swirl
2008-09-24 19:28             ` David Miller

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=1222186051.3545.13.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.com \
    --cc=davem@davemloft.net \
    --cc=javier@guerrag.com \
    --cc=kvm@vger.kernel.org \
    --cc=levon@movementarian.org \
    --cc=sparclinux@vger.kernel.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