From: Kun Wang <kun.kwang@gmail.com>
To: Alexander Graf <agraf@suse.de>
Cc: kvm-ppc@vger.kernel.org,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
Scott Wood <scottwood@freescale.com>,
Yoder Stuart-B08248 <B08248@freescale.com>
Subject: Re: KVM on IBM PowerEN processor
Date: Wed, 31 Aug 2011 00:49:20 +0800 [thread overview]
Message-ID: <4E5D1490.40000@gmail.com> (raw)
In-Reply-To: <4E5CB12D.1070802@suse.de>
于 2011-8-30 17:45, Alexander Graf 写道:
> Hi Kun,
>
> On 08/29/2011 11:31 AM, Kun Wang wrote:
>> Hi, everyone,
>>
>> This is Kun Wang from IBM Research China. I and my team have been
>> working
>> on IBM PowerEN processor in recent years, including its simulation,
>> lib/runtime optimization and etc. Now we start the work to enable KVM on
>> PowerEN processor. Since the A2 core of PowerEN follows Power ISA v2.06
>> (more specifically, book3e and 64-bit), I believe 99% of our work will
>> stick to the ISA, and hence can be leveraged by others.
>>
>> As the new one to this KVM world, I and my team definitely need your
>> help.
>> Looking forward to talking and working with you guys in the future.
>
> Welcome to the PowerPC KVM world! I'm looking very much forward to
> working with you there. Please always CC kvm@vger.kernel.org for
> emails you send to kvm-ppc@vger, unless you think of it as completely
> off-generic-kvm discussions. I like the idea of having more clever
> people involved in the PPC KVM process and by CC'ing kvm@vger, we get
> more exposure.
>
> The Freescale e500 cores are basically BookE 2.06 compliant with a few
> specialties here and there. Have you looked at their code? Sure, it's
> 32-bit as is now but there is definitely work going on at Freescale to
> get it 64-bit too.
>
> Maybe it makes sense to take the current code as a starting point and
> slowly move towards an architecture that is more generic. Maybe it
> makes sense to start from scratch and actually design something
> flexible that splits guest and host TLB code, so we could potentially
> run cross-book KVM in the future (which I would love to see happen!
> Just imagine running a PowerEN guest on a POWER7 system).
>
> Either way, please make sure to coordinate any efforts with me and
> Scott so we don't walk off in different directions and only get to
> realize we went down the wrong path when there's already a 100 patches
> patch set on the mailing list :)
>
>
> Again, welcome on board!
>
> Alex
>
>
Thanks, Alex.
Yes, we are aware of the e500 work done by Freescale folks. I agree with
you that we should coordinate together to achieve as more synergy.
Best regards,
Kun Wang
prev parent reply other threads:[~2011-08-30 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <OF86ED43B5.E5B63A29-ON482578FB.00344CC1-482578FB.00344AEB@cn.ibm.com>
2011-08-30 9:45 ` KVM on IBM PowerEN processor Alexander Graf
2011-08-30 14:15 ` Stuart Yoder
2011-08-30 16:31 ` Kun Wang
2011-09-12 12:18 ` Caraman Mihai Claudiu-B02008
2011-09-12 10:59 ` Benjamin Herrenschmidt
2011-08-30 16:49 ` Kun Wang [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=4E5D1490.40000@gmail.com \
--to=kun.kwang@gmail.com \
--cc=B08248@freescale.com \
--cc=agraf@suse.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=scottwood@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox