From: Pierre Morel <pmorel@linux.ibm.com>
To: Tony Krowiak <akrowiak@linux.vnet.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, schwidefsky@de.ibm.com,
heiko.carstens@de.ibm.com, borntraeger@de.ibm.com,
cohuck@redhat.com, david@redhat.com, bjsdjshi@linux.vnet.ibm.com,
pmorel@linux.vnet.ibm.com, alifm@linux.vnet.ibm.com,
mjrosato@linux.vnet.ibm.com, jjherne@linux.vnet.ibm.com,
pasic@linux.vnet.ibm.com, eskultet@redhat.com,
berrange@redhat.com, alex.williamson@redhat.com,
eric.auger@redhat.com, pbonzini@redhat.com,
peter.maydell@linaro.org, agraf@suse.de, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH v5 3/6] s390x/cpumodel: Set up CPU model for AP device support
Date: Tue, 15 May 2018 14:00:27 +0200 [thread overview]
Message-ID: <b43bdfdb-4c00-646d-efbd-1f411350929e@linux.ibm.com> (raw)
In-Reply-To: <1525782303-16940-4-git-send-email-akrowiak@linux.vnet.ibm.com>
On 08/05/2018 14:25, Tony Krowiak wrote:
> A new CPU model feature and two new CPU model facilities are
> introduced to support AP devices for a KVM guest.
>
> CPU model features:
>
> 1. The KVM_S390_VM_CPU_FEAT_AP CPU model feature indicates that
> AP facilities are installed. This feature will be enabled by
> the kernel only if the AP facilities are installed on the linux
> host. This feature must be turned on from userspace to access
> AP devices from the KVM guest. The QEMU command line to turn
> this feature looks something like this:
>
> qemu-system-s390x ... -cpu xxx,ap=on
>
> This feature will be supported for zEC12 and newer CPU models.
> The feature will not be supported for older models due to
> testability issues.
>
> CPU model facilities:
>
> 1. The S390_FEAT_AP_QUERY_CONFIG_INFO feature indicates the AP Query
> Configuration Information (QCI) facility is installed. This feature
> will be enabled by the kernel only if the QCI is installed on
> the host.
>
> 2. The S390_FEAT_AP_FACILITY_TEST feature indicates that the AP
> Facility Test (APFT) facility is installed. This feature will
> be enabled by the kernel only if the APFT facility is installed
> on the host.
>
> Signed-off-by: Tony Krowiak <akrowiak@linux.vnet.ibm.com>
> ---
> target/s390x/cpu_features.c | 3 +++
> target/s390x/cpu_features_def.h | 3 +++
> target/s390x/cpu_models.c | 2 ++
> target/s390x/gen-features.c | 3 +++
> target/s390x/kvm.c | 1 +
> 5 files changed, 12 insertions(+), 0 deletions(-)
>
> diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
> index 3b9e274..f344323 100644
> --- a/target/s390x/cpu_features.c
> +++ b/target/s390x/cpu_features.c
> @@ -40,8 +40,10 @@ static const S390FeatDef s390_features[] = {
> FEAT_INIT("srs", S390_FEAT_TYPE_STFL, 9, "Sense-running-status facility"),
> FEAT_INIT("csske", S390_FEAT_TYPE_STFL, 10, "Conditional-SSKE facility"),
> FEAT_INIT("ctop", S390_FEAT_TYPE_STFL, 11, "Configuration-topology facility"),
> + FEAT_INIT("apqci", S390_FEAT_TYPE_STFL, 12, "Query AP Configuration facility"),
Not a big deal, but why forget the I for "Information" in the long
description for APQCI
Also why not just "QCI" (I think it was already asked)
> FEAT_INIT("ipter", S390_FEAT_TYPE_STFL, 13, "IPTE-range facility"),
> FEAT_INIT("nonqks", S390_FEAT_TYPE_STFL, 14, "Nonquiescing key-setting facility"),
> + FEAT_INIT("apft", S390_FEAT_TYPE_STFL, 15, "Adjunct Processor Facilities Test facility"),
Not a big deal too, but you always use AP instead of Adjunct Processor,
why not here too?
> FEAT_INIT("etf2", S390_FEAT_TYPE_STFL, 16, "Extended-translation facility 2"),
> FEAT_INIT("msa-base", S390_FEAT_TYPE_STFL, 17, "Message-security-assist facility (excluding subfunctions)"),
> FEAT_INIT("ldisp", S390_FEAT_TYPE_STFL, 18, "Long-displacement facility"),
> @@ -129,6 +131,7 @@ static const S390FeatDef s390_features[] = {
>
> FEAT_INIT_MISC("dateh2", "DAT-enhancement facility 2"),
> FEAT_INIT_MISC("cmm", "Collaborative-memory-management facility"),
> + FEAT_INIT_MISC("ap", "AP instructions installed"),
>
> FEAT_INIT("plo-cl", S390_FEAT_TYPE_PLO, 0, "PLO Compare and load (32 bit in general registers)"),
> FEAT_INIT("plo-clg", S390_FEAT_TYPE_PLO, 1, "PLO Compare and load (64 bit in parameter list)"),
> diff --git a/target/s390x/cpu_features_def.h b/target/s390x/cpu_features_def.h
> index 7c5915c..8998b65 100644
> --- a/target/s390x/cpu_features_def.h
> +++ b/target/s390x/cpu_features_def.h
> @@ -27,8 +27,10 @@ typedef enum {
> S390_FEAT_SENSE_RUNNING_STATUS,
> S390_FEAT_CONDITIONAL_SSKE,
> S390_FEAT_CONFIGURATION_TOPOLOGY,
> + S390_FEAT_AP_QUERY_CONFIG_INFO,
> S390_FEAT_IPTE_RANGE,
> S390_FEAT_NONQ_KEY_SETTING,
> + S390_FEAT_AP_FACILITIES_TEST,
> S390_FEAT_EXTENDED_TRANSLATION_2,
> S390_FEAT_MSA,
> S390_FEAT_LONG_DISPLACEMENT,
> @@ -118,6 +120,7 @@ typedef enum {
> /* Misc */
> S390_FEAT_DAT_ENH_2,
> S390_FEAT_CMM,
> + S390_FEAT_AP,
>
> /* PLO */
> S390_FEAT_PLO_CL,
> diff --git a/target/s390x/cpu_models.c b/target/s390x/cpu_models.c
> index e10035a..5d834b4 100644
> --- a/target/s390x/cpu_models.c
> +++ b/target/s390x/cpu_models.c
> @@ -770,6 +770,8 @@ static void check_consistency(const S390CPUModel *model)
> { S390_FEAT_PRNO_TRNG_QRTCR, S390_FEAT_MSA_EXT_5 },
> { S390_FEAT_PRNO_TRNG, S390_FEAT_MSA_EXT_5 },
> { S390_FEAT_SIE_KSS, S390_FEAT_SIE_F2 },
> + { S390_FEAT_AP_QUERY_CONFIG_INFO, S390_FEAT_AP },
> + { S390_FEAT_AP_FACILITIES_TEST, S390_FEAT_AP },
> };
> int i;
>
> diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
> index 0cdbc15..0d5b0f7 100644
> --- a/target/s390x/gen-features.c
> +++ b/target/s390x/gen-features.c
> @@ -447,6 +447,9 @@ static uint16_t full_GEN12_GA1[] = {
> S390_FEAT_ADAPTER_INT_SUPPRESSION,
> S390_FEAT_EDAT_2,
> S390_FEAT_SIDE_EFFECT_ACCESS_ESOP2,
> + S390_FEAT_AP_QUERY_CONFIG_INFO,
> + S390_FEAT_AP_FACILITIES_TEST,
> + S390_FEAT_AP,
> };
>
> static uint16_t full_GEN12_GA2[] = {
> diff --git a/target/s390x/kvm.c b/target/s390x/kvm.c
> index 12b90cf..4d8c344 100644
> --- a/target/s390x/kvm.c
> +++ b/target/s390x/kvm.c
> @@ -2082,6 +2082,7 @@ static int kvm_to_feat[][2] = {
> { KVM_S390_VM_CPU_FEAT_PFMFI, S390_FEAT_SIE_PFMFI},
> { KVM_S390_VM_CPU_FEAT_SIGPIF, S390_FEAT_SIE_SIGPIF},
> { KVM_S390_VM_CPU_FEAT_KSS, S390_FEAT_SIE_KSS},
> + { KVM_S390_VM_CPU_FEAT_AP, S390_FEAT_AP},
> };
>
> static int query_cpu_feat(S390FeatBitmap features)
LGTM despite the two little things with which I do not agree 100%
Reviewed-by: Pierre Morel<pmorel@linux.vnet.ibm.com>
--
Pierre Morel
Linux/KVM/QEMU in Böblingen - Germany
next prev parent reply other threads:[~2018-05-15 12:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-08 12:24 [Qemu-devel] [PATCH v5 0/6] s390x: vfio-ap: guest dedicated crypto adapters Tony Krowiak
2018-05-08 12:24 ` [Qemu-devel] [PATCH v5 1/6] linux-headers: linux header updates for AP support Tony Krowiak
2018-05-08 12:24 ` [Qemu-devel] [PATCH v5 2/6] s390x/ap: base Adjunct Processor (AP) object Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 3/6] s390x/cpumodel: Set up CPU model for AP device support Tony Krowiak
2018-05-15 12:00 ` Pierre Morel [this message]
2018-05-15 15:03 ` Tony Krowiak
2018-05-16 9:05 ` Pierre Morel
2018-05-16 9:23 ` David Hildenbrand
2018-05-16 10:41 ` Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 4/6] s390x/vfio: ap: Introduce VFIO AP device Tony Krowiak
2018-05-09 14:28 ` Halil Pasic
2018-05-10 13:10 ` Tony Krowiak
2018-05-11 9:02 ` Pierre Morel
2018-05-14 19:26 ` Tony Krowiak
2018-05-15 7:55 ` Pierre Morel
2018-05-15 15:09 ` Tony Krowiak
2018-05-16 9:09 ` Pierre Morel
2018-05-16 10:43 ` Tony Krowiak
2018-05-11 10:29 ` Halil Pasic
2018-05-14 19:18 ` Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 5/6] s390: doc: detailed specifications for AP virtualization Tony Krowiak
2018-05-08 12:25 ` [Qemu-devel] [PATCH v5 6/6] MAINTAINERS: add entries for AP Tony Krowiak
2018-05-08 12:46 ` Cornelia Huck
2018-05-08 12:47 ` Cornelia Huck
2018-05-09 13:29 ` Tony Krowiak
2018-05-08 13:47 ` Halil Pasic
2018-05-09 13:30 ` Tony Krowiak
2018-05-09 3:46 ` Alexey Kardashevskiy
2018-05-09 13:28 ` Tony Krowiak
2018-05-08 12:48 ` [Qemu-devel] [PATCH v5 0/6] s390x: vfio-ap: guest dedicated crypto adapters no-reply
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=b43bdfdb-4c00-646d-efbd-1f411350929e@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=agraf@suse.de \
--cc=akrowiak@linux.vnet.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=alifm@linux.vnet.ibm.com \
--cc=berrange@redhat.com \
--cc=bjsdjshi@linux.vnet.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=eric.auger@redhat.com \
--cc=eskultet@redhat.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=mjrosato@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=pmorel@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).