From: Dale Farnsworth <dale@farnsworth.org>
To: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org
Cc: Avi Kivity <avi@redhat.com>
Subject: Re: KVM on MIPS?
Date: Fri, 26 Mar 2010 12:59:28 -0700 [thread overview]
Message-ID: <20100326195928.GA6472@farnsworth.org> (raw)
In-Reply-To: <20100326161619.GA31195@farnsworth.org>
On Fri, Mar 26, 2010 at 09:16:19AM -0700, Dale Farnsworth wrote:
> On Thu, Mar 25, 2010 at 11:32:57PM +0100, Alexander Graf wrote:
> >
> > Am 25.03.2010 um 22:04 schrieb Avi Kivity <avi@redhat.com>:
> >
> >> 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.
> >>
> >>> 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?
> >
> > FWIW it's not. Kernel mode is used based on an address offset of the IP.
> > Since you'd want to have your guest running in user mode, you're pretty
> > much lost there.
>
> I guess that would qualify as a pitfall. Thanks Avi and Alex.
After thinking about this some more, I think this means we can't run
an unmodified guest. It should be possible to build the guest kernel
to run in supervisor or user mode/address space.
I'm new to MIPS, so I'm still looking for other challenges in virtualizing
the instruction set.
-Dale
next prev parent reply other threads:[~2010-03-26 19:59 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
2010-03-25 22:32 ` Alexander Graf
2010-03-26 16:16 ` Dale Farnsworth
2010-03-26 19:59 ` Dale Farnsworth [this message]
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=20100326195928.GA6472@farnsworth.org \
--to=dale@farnsworth.org \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.