From: Avi Kivity <avi@redhat.com>
To: Dale Farnsworth <dale@farnsworth.org>
Cc: kvm@vger.kernel.org
Subject: Re: KVM on MIPS?
Date: Thu, 25 Mar 2010 23:04:43 +0200 [thread overview]
Message-ID: <4BABCFEB.9050409@redhat.com> (raw)
In-Reply-To: <20100325165442.GA21343@farnsworth.org>
On 03/25/2010 06:54 PM, Dale Farnsworth wrote:
> I'm beginning to look at implementing KVM on MIPS. I've tried to search
> for any work-in-progress on this but haven't found much at all.
>
Google comes up with some hits, but nothing concrete.
> If you know of anyone who is working on this or of pitfalls I should
> consider before jumping in, please let me know.
>
Is the instruction set virtualizable? Are you planning full virt or
paravirt?
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
next prev parent reply other threads:[~2010-03-25 21:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-25 16:54 KVM on MIPS? Dale Farnsworth
2010-03-25 21:04 ` Avi Kivity [this message]
2010-03-25 22:32 ` Alexander Graf
2010-03-26 16:16 ` Dale Farnsworth
2010-03-26 19:59 ` Dale Farnsworth
2010-03-27 1:09 ` Nolan
2010-08-12 21:26 ` Hollis Blanchard
2010-08-13 4:24 ` Dale Farnsworth
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=4BABCFEB.9050409@redhat.com \
--to=avi@redhat.com \
--cc=dale@farnsworth.org \
--cc=kvm@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