Kernel KVM-PPC virtualization development
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: Michael Neuling <mikey@neuling.org>
Cc: benh@kernel.crashing.org, Paul Mackerras <paulus@samba.org>,
	kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Subject: Re: [PATCH v3] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg
Date: Tue, 03 Sep 2013 15:29:24 +0000	[thread overview]
Message-ID: <52260054.10807@suse.de> (raw)
In-Reply-To: <14028.1378170792@ale.ozlabs.ibm.com>

On 09/03/2013 03:13 AM, Michael Neuling wrote:
> This reserves space in get/set_one_reg ioctl for the extra guest state
> needed for POWER8.  It doesn't implement these at all, it just reserves
> them so that the ABI is defined now.
>
> A few things to note here:
>
> - This add *a lot* state for transactional memory.  TM suspend mode,
>    this is unavoidable, you can't simply roll back all transactions and
>    store only the checkpointed state.  I've added this all to
>    get/set_one_reg (including GPRs) rather than creating a new ioctl
>    which returns a struct kvm_regs like KVM_GET_REGS does.  This means we
>    if we need to extract the TM state, we are going to need a bucket load
>    of IOCTLs.  Hopefully most of the time this will not be needed as we
>    can look at the MSR to see if TM is active and only grab them when
>    needed.  If this becomes a bottle neck in future we can add another
>    ioctl to grab all this state in one go.
>
> - The TM state is offset by 0x80000000.
>
> - For TM, I've done away with VMX and FP and created a single 64x128 bit
>    VSX register space.
>
> - I've left a space of 1 (at 0x9c) since Paulus needs to add a value
>    which applies to POWER7 as well.
>
> Signed-off-by: Michael Neuling<mikey@neuling.org>

Thanks, applied to kvm-ppc-queue.


Alex


      reply	other threads:[~2013-09-03 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-30  6:09 [PATCH RFC] KVM: PPC: Book3S HV: Reserve POWER8 space in get/set_one_reg Michael Neuling
2013-08-30 14:01 ` Alexander Graf
2013-08-30 22:17   ` Benjamin Herrenschmidt
2013-08-30 22:21     ` Michael Neuling
2013-08-30 22:22   ` Michael Neuling
2013-09-03  0:57 ` [PATCH v2] " Michael Neuling
2013-09-03  1:13   ` [PATCH v3] " Michael Neuling
2013-09-03 15:29     ` Alexander Graf [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=52260054.10807@suse.de \
    --to=agraf@suse.de \
    --cc=benh@kernel.crashing.org \
    --cc=kvm-ppc@vger.kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=mikey@neuling.org \
    --cc=paulus@samba.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