From: Avi Kivity <avi@redhat.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-ppc@vger.kernel.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 00 of 16] port KVM to PowerPC e500
Date: Sun, 04 Jan 2009 11:02:33 +0000 [thread overview]
Message-ID: <49609749.9050202@redhat.com> (raw)
In-Reply-To: <patchbomb.1231021377@localhost.localdomain>
Hollis Blanchard wrote:
> Hi Avi, these patches add support for Freescale's e500 (v2) core. I did some
> refactoring, but the actual port was done by Liu Yu at Freescale. Please
> apply.
>
> e500 is a 32-bit PowerPC "Book E" core (as is IBM/AMCC's 440) found in a
> variety of Freescale SoCs. It uses a software-managed TLB and no hardware
> tablewalk.
>
> (These patches do not contain support for Freescale's announced e500mc core,
> which implements virtualization features in hardware.)
>
Applied, thanks.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-01-04 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-03 22:22 [PATCH 00 of 16] port KVM to PowerPC e500 Hollis Blanchard
2009-01-04 11:02 ` Avi Kivity [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=49609749.9050202@redhat.com \
--to=avi@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=kvm-ppc@vger.kernel.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