From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Caraman Mihai Claudiu-B02008 <B02008@freescale.com>
Cc: "kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description
Date: Thu, 25 Apr 2013 17:16:51 +0800 [thread overview]
Message-ID: <5178F483.9010001@windriver.com> (raw)
In-Reply-To: <300B73AA675FCE4A93EB4FC1D42459FF3D94D7@039-SN2MPN1-013.039d.mgd.msft.net>
On 04/25/2013 05:09 PM, Caraman Mihai Claudiu-B02008 wrote:
>> -----Original Message-----
>> From: tiejun.chen [mailto:tiejun.chen@windriver.com]
>> Sent: Friday, April 19, 2013 1:03 PM
>> To: Caraman Mihai Claudiu-B02008
>> Cc: kvm-ppc@vger.kernel.org; kvm@vger.kernel.org
>> Subject: Re: [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig
>> description
>>
>> On 04/11/2013 06:03 PM, Mihai Caraman wrote:
>>> Add e6500 core to Kconfig description.
>>>
>>> Signed-off-by: Mihai Caraman <mihai.caraman@freescale.com>
>>> ---
>>> v3:
>>> - No change
>>>
>>> arch/powerpc/kvm/Kconfig | 6 +++---
>>> 1 files changed, 3 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/arch/powerpc/kvm/Kconfig b/arch/powerpc/kvm/Kconfig
>>> index 63c67ec..4489520 100644
>>> --- a/arch/powerpc/kvm/Kconfig
>>> +++ b/arch/powerpc/kvm/Kconfig
>>> @@ -136,15 +136,15 @@ config KVM_E500V2
>>> If unsure, say N.
>>>
>>> config KVM_E500MC
>>> - bool "KVM support for PowerPC E500MC/E5500 processors"
>>> + bool "KVM support for PowerPC E500MC/E5500/E6500 processors"
>>> depends on PPC_E500MC
>>> select KVM
>>> select KVM_MMIO
>>> select KVM_BOOKE_HV
>>> select MMU_NOTIFIER
>>> ---help---
>>> - Support running unmodified E500MC/E5500 (32-bit) guest kernels in
>>
>> I ever tried p5040ds but failed with 64-bit, but looks are you saying
>> this patch
>> set can make e5500/e6500 work well with 64-bit? If so, will we need to
>> upgrade
>> qemu or something else like dtb?
>
> KVM should work on p5040ds with and without this patchset. The latest
> qemu requires this patch: "powerpc: Add paravirt idle loop for 64-bit Book-E",
> you will not pass guest udev without it.
Which should qemu tree be used here?
My tree is cloned from:
git://repo.or.cz/qemu/agraf.git ppc-next
But I can't find this commit.
Tiejun
next prev parent reply other threads:[~2013-04-25 9:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-25 9:09 [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description Caraman Mihai Claudiu-B02008
2013-04-25 9:16 ` tiejun.chen [this message]
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D967A@039-SN2MPN1-013.039d.mgd.msft.net>
2013-04-25 9:49 ` tiejun.chen
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D997F@039-SN2MPN1-013.039d.mgd.msft.net>
[not found] ` <51791195.7090909@windriver.com>
[not found] ` <300B73AA675FCE4A93EB4FC1D42459FF3D9A8A@039-SN2MPN1-013.039d.mgd.msft.net>
2013-04-26 3:11 ` tiejun.chen
2013-04-26 9:38 ` tiejun.chen
-- strict thread matches above, loose matches on Subject: below --
2013-04-11 10:03 [PATCH 0/8 v3] KVM: PPC: e500: Enable FSL e6500 core Mihai Caraman
2013-04-11 10:03 ` [PATCH 8/8 v3] KVM: PPC: e500: Add e6500 core to Kconfig description Mihai Caraman
2013-04-19 10:03 ` tiejun.chen
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=5178F483.9010001@windriver.com \
--to=tiejun.chen@windriver.com \
--cc=B02008@freescale.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