From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] sparc kqemu?
Date: Sun, 19 Aug 2007 21:00:23 +0300 [thread overview]
Message-ID: <f43fc5580708191100m705c4728y2cfb65769d8b8f29@mail.gmail.com> (raw)
In-Reply-To: <db7b3ca90708161324n6fdf45bdkd7279a6eb2c19d25@mail.gmail.com>
On 8/16/07, Jonathan Kalbfeld <jonathan.kalbfeld@gmail.com> wrote:
> Is this on the horizon? Is there any interest in it?
For Sparc32 this could be possible, the page table structures are not
unlike i386 ones. Given the death of Sparc32 distros I don't think
there would be much interest.
On Sparc64 there are no in-memory structures for MMU, instead page
table entries are pushed into TLB when needed. I think kqemu would
have to mess with the OS page structures or install its own TLB
handler.
As Sparc architecture is much better on virtualisation than x86, it
should be possible to port kvm instead.
prev parent reply other threads:[~2007-08-19 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-16 20:24 [Qemu-devel] sparc kqemu? Jonathan Kalbfeld
2007-08-19 18:00 ` Blue Swirl [this message]
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=f43fc5580708191100m705c4728y2cfb65769d8b8f29@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).