From: Hollis Blanchard <hollisb@us.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 0 of 7] [RFC] kvm ppc refactoring
Date: Mon, 29 Sep 2008 18:54:12 +0000 [thread overview]
Message-ID: <1222714452.11272.35.camel@localhost.localdomain> (raw)
In-Reply-To: <patchbomb.1222713389@localhost.localdomain>
On Mon, 2008-09-29 at 20:40 +0200, Alexander Graf wrote:
> On 29.09.2008, at 20:36, Hollis Blanchard wrote:
>
> > These patches refactor the KVM PPC code to support non-Book E
> > processors. The
> > Book E code might need a little more work to support e500, but
> > probably not
> > much. Beyond this, we still need to split struct kvm_vcpu_arch using
> > container_of() macros.
> >
> > There's a lot of code movement, so it might be easier to review by
> > examining
> > the final result. Basically we have powerpc.c and emulate.c calling
> > core-specific functions, some of which are provided by booke.c and
> > some by
> > 44x*.c.
> >
> > Comments?
>
> Does non-Book E processors mean 97x series :-)?
That's not something I'm personally looking at right now, but this patch
series would get you closer. :)
Probably the most feasible would be to ignore 970's hypervisor mode
(since you can't use it on any generally available platforms anyways),
and implement 440-style software-only virtualization instead. I've heard
people dreaming about doing exactly that for Cell (same problem).
If you want to chat about how exactly this could be implemented, I'd be
happy to brainstorm with you... :)
--
Hollis Blanchard
IBM Linux Technology Center
prev parent reply other threads:[~2008-09-29 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-29 18:36 [PATCH 0 of 7] [RFC] kvm ppc refactoring Hollis Blanchard
2008-09-29 18:40 ` Alexander Graf
2008-09-29 18:54 ` Hollis Blanchard [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=1222714452.11272.35.camel@localhost.localdomain \
--to=hollisb@us.ibm.com \
--cc=kvm-ppc@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.