kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>, kvm-ppc@vger.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH 0/6] KVM: PPC: Book3S PR: Add POWER8 support
Date: Sun, 04 May 2014 22:06:36 +0530	[thread overview]
Message-ID: <87zjixa4bv.fsf@linux.vnet.ibm.com> (raw)
In-Reply-To: <1398788262-3307-1-git-send-email-agraf@suse.de>

Alexander Graf <agraf@suse.de> writes:

> When running on a POWER8 host, we get away with running the guest as POWER7
> and nothing falls apart.
>
> However, when we start exposing POWER8 as guest CPU, guests will start using
> new abilities on POWER8 which we need to handle.
>
> This patch set does a minimalistic approach to implementing those bits to
> make guests happy enough to run.
>
>
> Alex
>
> Alexander Graf (6):
>   KVM: PPC: Book3S PR: Ignore PMU SPRs
>   KVM: PPC: Book3S PR: Emulate TIR register
>   KVM: PPC: Book3S PR: Handle Facility interrupt and FSCR
>   KVM: PPC: Book3S PR: Expose TAR facility to guest
>   KVM: PPC: Book3S PR: Expose EBB registers
>   KVM: PPC: Book3S PR: Expose TM registers
>
>  arch/powerpc/include/asm/kvm_asm.h        | 18 ++++---
>  arch/powerpc/include/asm/kvm_book3s_asm.h |  2 +
>  arch/powerpc/include/asm/kvm_host.h       |  3 ++
>  arch/powerpc/kernel/asm-offsets.c         |  3 ++
>  arch/powerpc/kvm/book3s.c                 | 34 +++++++++++++
>  arch/powerpc/kvm/book3s_emulate.c         | 53 ++++++++++++++++++++
>  arch/powerpc/kvm/book3s_hv.c              | 30 -----------
>  arch/powerpc/kvm/book3s_pr.c              | 82 +++++++++++++++++++++++++++++++
>  arch/powerpc/kvm/book3s_segment.S         | 25 ++++++++++
>  9 files changed, 212 insertions(+), 38 deletions(-)
>

I did most of this as part of 

[RFC PATCH 01/10] KVM: PPC: BOOK3S: PR: Add POWER8 support
http://mid.gmane.org/1390927455-3312-1-git-send-email-aneesh.kumar@linux.vnet.ibm.com

Any reason why that is not picked up ? TM was the reason I didn't push the
patchset again. I was not sure how to get all the TM details to
work.

-aneesh


  parent reply	other threads:[~2014-05-04 16:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-29 16:17 [PATCH 0/6] KVM: PPC: Book3S PR: Add POWER8 support Alexander Graf
2014-04-29 16:17 ` [PATCH 1/6] KVM: PPC: Book3S PR: Ignore PMU SPRs Alexander Graf
2014-04-30 22:12   ` Paul Mackerras
2014-05-02  8:35     ` Alexander Graf
2014-05-07  7:09       ` Paul Mackerras
2014-05-08 12:11         ` Alexander Graf
2014-04-29 16:17 ` [PATCH 2/6] KVM: PPC: Book3S PR: Emulate TIR register Alexander Graf
2014-04-30  5:51   ` Michael Neuling
2014-04-30 10:06     ` Alexander Graf
2014-04-29 16:17 ` [PATCH 3/6] KVM: PPC: Book3S PR: Handle Facility interrupt and FSCR Alexander Graf
2014-04-29 16:17 ` [PATCH 4/6] KVM: PPC: Book3S PR: Expose TAR facility to guest Alexander Graf
2014-04-29 16:17 ` [PATCH 5/6] KVM: PPC: Book3S PR: Expose EBB registers Alexander Graf
2014-04-29 16:17 ` [PATCH 6/6] KVM: PPC: Book3S PR: Expose TM registers Alexander Graf
2014-05-17  6:20   ` Paul Mackerras
2014-05-19 13:09     ` Alexander Graf
2014-05-20  9:59       ` Paul Mackerras
2014-05-20 11:49         ` Alexander Graf
2014-05-04 16:36 ` Aneesh Kumar K.V [this message]
2014-05-05 11:18   ` [PATCH 0/6] KVM: PPC: Book3S PR: Add POWER8 support Alexander Graf
2014-05-05 14:38     ` Aneesh Kumar K.V
2014-05-05 14:42       ` Alexander Graf
2014-05-05 14:48         ` Aneesh Kumar K.V

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=87zjixa4bv.fsf@linux.vnet.ibm.com \
    --to=aneesh.kumar@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --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;
as well as URLs for NNTP newsgroup(s).