public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: Mihai Caraman <mihai.caraman@freescale.com>
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
Date: Fri, 19 Apr 2013 18:03:29 +0800	[thread overview]
Message-ID: <51711671.3070004@windriver.com> (raw)
In-Reply-To: <1365674594-17410-9-git-send-email-mihai.caraman@freescale.com>

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?

Tiejun

> -	  virtual machines on E500MC/E5500 host processors.
> +	  Support running unmodified E500MC/E5500/E6500 guest kernels in
> +	  virtual machines on E500MC/E5500/E6500 host processors.
>
>   	  This module provides access to the hardware capabilities through
>   	  a character device node named /dev/kvm.
>

  reply	other threads:[~2013-04-19 10:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 10:03 [PATCH 0/8 v3] KVM: PPC: e500: Enable FSL e6500 core Mihai Caraman
2013-04-11 10:03 ` [PATCH 1/8 v3] KVM: PPC: Book3E: Refactor ONE_REG ioctl implementation Mihai Caraman
2013-04-11 10:03 ` [PATCH 2/8 v3] KVM: PPC: e500: Expose MMU registers via ONE_REG Mihai Caraman
2013-04-11 10:03 ` [PATCH 3/8 v3] KVM: PPC: e500: Move vcpu's MMU configuration to dedicated functions Mihai Caraman
2013-04-11 10:03 ` [PATCH 4/8 v3] KVM: PPC: e500: Add support for TLBnPS registers Mihai Caraman
2013-04-11 10:03 ` [PATCH 5/8] KVM: PPC: e500: Add support for EPTCFG register Mihai Caraman
2013-04-11 10:03 ` [PATCH 6/8 v3] KVM: PPC: e500: Remove E.PT and E.HV.LRAT categories from VCPUs Mihai Caraman
2013-04-11 10:03 ` [PATCH 7/8 v3] KVM: PPC: e500mc: Enable e6500 cores 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 [this message]
2013-04-26 13:48 ` [PATCH 0/8 v3] KVM: PPC: e500: Enable FSL e6500 core Alexander Graf
  -- strict thread matches above, loose matches on Subject: below --
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
     [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

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=51711671.3070004@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mihai.caraman@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