All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Mackerras <paulus@ozlabs.org>
To: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Report storage key support to userspace
Date: Thu, 31 Aug 2017 13:43:30 +1000	[thread overview]
Message-ID: <20170831034330.GF22549@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20170825095339.GC14035@fergus.ozlabs.ibm.com>

On Fri, Aug 25, 2017 at 07:53:39PM +1000, Paul Mackerras wrote:
> This adds information about storage keys to the struct returned by
> the KVM_PPC_GET_SMMU_INFO ioctl.  The new fields replace a pad field,
> which was zeroed by previous kernel versions.  Thus userspace that
> knows about the new fields will see zeroes when running on an older
> kernel, indicating that storage keys are not supported.  The size of
> the structure has not changed.
> 
> The number of keys is hard-coded for the CPUs supported by HV KVM,
> which is just POWER7, POWER8 and POWER9.
> 
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>

Patch applied to my kvm-ppc-next branch.

Paul.

WARNING: multiple messages have this Message-ID (diff)
From: Paul Mackerras <paulus@ozlabs.org>
To: kvm@vger.kernel.org, kvm-ppc@vger.kernel.org
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] KVM: PPC: Book3S HV: Report storage key support to userspace
Date: Thu, 31 Aug 2017 03:43:30 +0000	[thread overview]
Message-ID: <20170831034330.GF22549@fergus.ozlabs.ibm.com> (raw)
In-Reply-To: <20170825095339.GC14035@fergus.ozlabs.ibm.com>

On Fri, Aug 25, 2017 at 07:53:39PM +1000, Paul Mackerras wrote:
> This adds information about storage keys to the struct returned by
> the KVM_PPC_GET_SMMU_INFO ioctl.  The new fields replace a pad field,
> which was zeroed by previous kernel versions.  Thus userspace that
> knows about the new fields will see zeroes when running on an older
> kernel, indicating that storage keys are not supported.  The size of
> the structure has not changed.
> 
> The number of keys is hard-coded for the CPUs supported by HV KVM,
> which is just POWER7, POWER8 and POWER9.
> 
> Signed-off-by: Paul Mackerras <paulus@ozlabs.org>

Patch applied to my kvm-ppc-next branch.

Paul.

  parent reply	other threads:[~2017-08-31  3:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-25  9:53 [PATCH] KVM: PPC: Book3S HV: Report storage key support to userspace Paul Mackerras
2017-08-25  9:53 ` Paul Mackerras
2017-08-27  3:19 ` David Gibson
2017-08-27  3:19   ` David Gibson
2017-08-31  3:43 ` Paul Mackerras [this message]
2017-08-31  3:43   ` Paul Mackerras

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=20170831034330.GF22549@fergus.ozlabs.ibm.com \
    --to=paulus@ozlabs.org \
    --cc=david@gibson.dropbear.id.au \
    --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 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.