All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
To: kvm-ppc@vger.kernel.org
Subject: Re: [PATCH 4/4] add e500 support for kvm
Date: Thu, 21 Aug 2008 14:29:19 +0000	[thread overview]
Message-ID: <48AD7BBF.9000107@linux.vnet.ibm.com> (raw)
In-Reply-To: <1218790228-19549-5-git-send-email-yu.liu@freescale.com>

Liu Yu wrote:
> Any chance we could merge struct kvm_vcpu_arch for both 44x and e500?
>
>   
In the end we might end up needing
vcpu                    -> arch                -> core
kvm things         power arch         core specific things

Hollis is working on better abstraction and restructuring code anyway so 
he might have a more detailed opinion ;-)

> Signed-off-by: Liu Yu <yu.liu@freescale.com>
> ---
>  arch/powerpc/include/asm/kvm_asm.h  |    7 ++-
>  arch/powerpc/include/asm/kvm_host.h |  112 +++++++++++++++++++++++++++++++++++
>  arch/powerpc/kernel/asm-offsets.c   |    9 +++
>  arch/powerpc/kvm/44x_tlb.h          |    4 +
>  arch/powerpc/kvm/Kconfig            |    4 +-
>  arch/powerpc/kvm/Makefile           |    7 ++
>  arch/powerpc/kvm/booke_guest.c      |   14 ++++-
>  arch/powerpc/kvm/booke_host.c       |   20 ++++--
>  arch/powerpc/kvm/emulate.c          |   88 +++++++++++++++++++++++++++-
>  arch/powerpc/kvm/powerpc.c          |    4 +
>  arch/powerpc/kvm/powerpc.h          |    4 +
>  11 files changed, 261 insertions(+), 12 deletions(-)
>
>   
[...]

-- 

Grüsse / regards, 
Christian Ehrhardt
IBM Linux Technology Center, Open Virtualization


  reply	other threads:[~2008-08-21 14:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-15  8:50 [PATCH 4/4] add e500 support for kvm Liu Yu
2008-08-21 14:29 ` Christian Ehrhardt [this message]
2008-08-22  8:07 ` Liu Yu

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=48AD7BBF.9000107@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=kvm-ppc@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 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.