From: Frederic Konrad <fred.konrad@greensocs.com>
To: Alexander Graf <agraf@suse.de>
Cc: Mark Burton <mark.burton@greensocs.com>,
qemu-devel <qemu-devel@nongnu.org>,
"stuart.yoder@freescale.com" <stuart.yoder@freescale.com>
Subject: Re: [Qemu-devel] E6500 inside QEMU?
Date: Wed, 09 Jul 2014 14:00:06 +0200 [thread overview]
Message-ID: <53BD2EC6.8000204@greensocs.com> (raw)
In-Reply-To: <D276E65A-AF96-4023-A179-45B58182E707@suse.de>
On 09/07/2014 11:46, Alexander Graf wrote:
>
>> Am 09.07.2014 um 10:26 schrieb Frederic Konrad <fred.konrad@greensocs.com>:
>>
>> Hi,
>>
>> I saw some patches about E6500 cpu on the mailing list.
>>
>> here: http://qemu.11.n7.nabble.com/PATCH-1-2-QEMU-PPC-specify-PVRs-for-all-e500-cores-td248146.html
>>
>> What is the status of E6500 upstream?
> That patch only added the PVR values for use with KVM. We don't have any support for 6500 specific features yet (threading, hw table walk, Altivec. Though Altivec emulation does exist already, so that'd mostly be a matter of plumbing it into the booke exception paths.
>
>
> Alex
>
Ok that's what I thought :).
Thanks for the clarification!
Fred
prev parent reply other threads:[~2014-07-09 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-09 8:26 [Qemu-devel] E6500 inside QEMU? Frederic Konrad
2014-07-09 9:46 ` Alexander Graf
2014-07-09 12:00 ` Frederic Konrad [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=53BD2EC6.8000204@greensocs.com \
--to=fred.konrad@greensocs.com \
--cc=agraf@suse.de \
--cc=mark.burton@greensocs.com \
--cc=qemu-devel@nongnu.org \
--cc=stuart.yoder@freescale.com \
/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.