From: Anthony Liguori <anthony@codemonkey.ws>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: kvm@vger.kernel.org, sparclinux@vger.kernel.org,
John Levon <levon@movementarian.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: KVM for Sparc?
Date: Mon, 22 Sep 2008 14:34:21 -0500 [thread overview]
Message-ID: <48D7F33D.90007@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580809210552sdf3ee24w8922ac25f93fb75@mail.gmail.com>
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.
KVM has code to do shadow paging and also software TLB virtualization,
so depending on how Sparc manages the TLB, it should be pretty straight
forward to base the Sparc code from the appropriate code that already
exists.
> Other possibilities include porting kqemu or Xen, but I think KVM has
> the brightest future.
>
> I'm interested in pushing the Qemu side forward, but obviously
> something needs to be done by the kernel/KVM people too.
KVM supports x86, ia64, s390, and PPC today. I don't think there would
be any problems adding another architecture support. Almost all of the
abstractions should have been flushed out already by the previous
architecture ports. Moreover, since there is already good support for
Sparc in QEMU, that should simplify things significantly.
I'm looking forward to seeing the progress you make!
Regards,
Anthony Liguori
> What is the
> feeling on KVM and Sparclinux side?
> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2008-09-22 19:35 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 [this message]
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
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=48D7F33D.90007@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=blauwirbel@gmail.com \
--cc=hollisb@us.ibm.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