public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	kvm@vger.kernel.org, sparclinux@vger.kernel.org,
	John Levon <levon@movementarian.org>
Subject: Re: KVM for Sparc?
Date: Mon, 22 Sep 2008 15:18:39 -0500	[thread overview]
Message-ID: <1222114719.3967.43.camel@localhost.localdomain> (raw)
In-Reply-To: <48D7F33D.90007@codemonkey.ws>

On Mon, 2008-09-22 at 14:34 -0500, Anthony Liguori wrote:
> Blue Swirl wrote:
> > Hi,
> >
> >  Sorry for cross-posting (and because I used the wrong address in the
> > first time for KVM, sorry for the duplicate on Sparclinux).
> >
> >  Sparc host support for Qemu is getting close
> >  to ready, I can already run a Sparc32 system emulator on
> >  OpenBSD/Sparc64 and there is some limited success with recent glibc on
> >  Linux/Sparc64. Otherwise Sparc32 target emulator is pretty stable.
> >  Sparc64 target emulator can boot from several CD images, but crashes
> >  pretty soon.
> >
> >  But I think we could already start early drafting of what KVM support
> >  for Sparc32 and Sparc64 would mean. Because of certain problems in the
> >  V9 instruction set design (V8 rett reuse for example), it may be
> >  difficult or even impossible to use an accelerator if the host and
> >  target instruction sets do not match.
> >   
> 
> I don't know much about the Sparc architecture, but the embedded PowerPC 
> port that Hollis has spear-headed is for an architecture that does not 
> natively support hardware virtualization.  As long as Sparc meets all of 
> the requirements to do this sort of virtualization (all privileged 
> instructions are trappable when run in non-privileged mode), it should 
> be rather straight forward.

It would be even more interesting to implement host support on the Sparc
processors with hardware virtualization support.

Without that, functionality is possible (as we've demonstrated with KVM
on PPC440)... the trick is performance.

-- 
Hollis Blanchard
IBM Linux Technology Center


  reply	other threads:[~2008-09-22 20:18 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 [this message]
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
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=1222114719.3967.43.camel@localhost.localdomain \
    --to=hollisb@us.ibm.com \
    --cc=anthony@codemonkey.ws \
    --cc=blauwirbel@gmail.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