From: David Hildenbrand <david@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
qemu-s390x <qemu-s390x@nongnu.org>,
Alexander Graf <agraf@suse.de>, Thomas Huth <thuth@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Janosch Frank <frankja@linux.vnet.ibm.com>,
Halil Pasic <pasic@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 3/3] s390x/kvm: provide stfle.81
Date: Wed, 17 Jan 2018 22:59:55 +0100 [thread overview]
Message-ID: <7aa14ddf-769f-2c79-4ca4-fa4b0aa65347@redhat.com> (raw)
In-Reply-To: <7cc4f08f-2d40-1a1a-0e52-71cb310c3c0a@de.ibm.com>
On 17.01.2018 22:37, Christian Borntraeger wrote:
>
>
> On 01/17/2018 10:13 PM, David Hildenbrand wrote:
>> On 17.01.2018 20:37, Christian Borntraeger wrote:
>>> stfle.81 (ppa15) is a transparent facility that can be passed to the
>>> guest without the need to implement hypervisor support. As this feature
>>> can be provided by firmware we add it to all full models.
>>>
>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>> ---
>>> target/s390x/cpu_features.c | 1 +
>>> target/s390x/cpu_features_def.h | 1 +
>>> target/s390x/gen-features.c | 1 +
>>> 3 files changed, 3 insertions(+)
>>>
>>> diff --git a/target/s390x/cpu_features.c b/target/s390x/cpu_features.c
>>> index 5d1c210..1550ab0 100644
>>> --- a/target/s390x/cpu_features.c
>>> +++ b/target/s390x/cpu_features.c
>>> @@ -89,6 +89,7 @@ static const S390FeatDef s390_features[] = {
>>> FEAT_INIT("msa4-base", S390_FEAT_TYPE_STFL, 77, "Message-security-assist-extension-4 facility (excluding subfunctions)"),
>>> FEAT_INIT("edat2", S390_FEAT_TYPE_STFL, 78, "Enhanced-DAT facility 2"),
>>> FEAT_INIT("dfppc", S390_FEAT_TYPE_STFL, 80, "Decimal-floating-point packed-conversion facility"),
>>> + FEAT_INIT("ppa15", S390_FEAT_TYPE_STFL, 81, "PPA15 is installed"),
>>> FEAT_INIT("bpb", S390_FEAT_TYPE_STFL, 82, "Branch Prediction Blocking"),
>>> FEAT_INIT("vx", S390_FEAT_TYPE_STFL, 129, "Vector facility"),
>>> FEAT_INIT("iep", S390_FEAT_TYPE_STFL, 130, "Instruction-execution-protection facility"),
>>> diff --git a/target/s390x/cpu_features_def.h b/target/s390x/cpu_features_def.h
>>> index 4487cfd..4d93087 100644
>>> --- a/target/s390x/cpu_features_def.h
>>> +++ b/target/s390x/cpu_features_def.h
>>> @@ -80,6 +80,7 @@ typedef enum {
>>> S390_FEAT_MSA_EXT_4,
>>> S390_FEAT_EDAT_2,
>>> S390_FEAT_DFP_PACKED_CONVERSION,
>>> + S390_FEAT_PPA15,
>>> S390_FEAT_BPB,
>>> S390_FEAT_VECTOR,
>>> S390_FEAT_INSTRUCTION_EXEC_PROT,
>>> diff --git a/target/s390x/gen-features.c b/target/s390x/gen-features.c
>>> index 95ee870..50bd3f4 100644
>>> --- a/target/s390x/gen-features.c
>>> +++ b/target/s390x/gen-features.c
>>> @@ -357,6 +357,7 @@ static uint16_t full_GEN7_GA1[] = {
>>> S390_FEAT_SIE_GPERE,
>>> S390_FEAT_SIE_IB,
>>> S390_FEAT_SIE_CEI,
>>> + S390_FEAT_PPA15,
>>> S390_FEAT_BPB,
>>
>
>> Is the order in this list still correct?
>
> Is the order in this array important as well? It seems to work fine. At least PPA15 is correctly
> ordered vs BPB.
>
Purely style. (when introducing, I tried to keep features in the same
order as defined in target/s390x/cpu_features_def.h )
So feel free to keep the order (or I'll clean this up again one day).
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2018-01-17 22:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-17 19:37 [Qemu-devel] [PATCH v2 0/3] s390x/kvm: implement new hardware/firmware features Christian Borntraeger
2018-01-17 19:37 ` [Qemu-devel] [PATCH v2 1/3] header sync Christian Borntraeger
2018-01-17 19:46 ` Eric Blake
2018-01-17 20:02 ` Christian Borntraeger
2018-01-17 21:02 ` David Hildenbrand
2018-01-17 19:37 ` [Qemu-devel] [PATCH v2 2/3] s390x/kvm: Handle bpb feature Christian Borntraeger
2018-01-17 21:12 ` David Hildenbrand
2018-01-18 7:03 ` Thomas Huth
2018-01-17 19:37 ` [Qemu-devel] [PATCH v2 3/3] s390x/kvm: provide stfle.81 Christian Borntraeger
2018-01-17 21:13 ` David Hildenbrand
2018-01-17 21:37 ` Christian Borntraeger
2018-01-17 21:59 ` David Hildenbrand [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=7aa14ddf-769f-2c79-4ca4-fa4b0aa65347@redhat.com \
--to=david@redhat.com \
--cc=agraf@suse.de \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=frankja@linux.vnet.ibm.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.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).