From: Cornelia Huck <cohuck@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-devel <qemu-devel@nongnu.org>,
Halil Pasic <pasic@linux.ibm.com>,
qemu-s390x <qemu-s390x@nongnu.org>
Subject: Re: [PATCH 1/1] s390x/cpumodel: add 3931 and 3932
Date: Wed, 30 Jun 2021 17:32:04 +0200 [thread overview]
Message-ID: <8735szl66j.fsf@redhat.com> (raw)
In-Reply-To: <7cd6fb75-521b-e970-4f25-b23722765bf9@de.ibm.com>
On Wed, Jun 30 2021, Christian Borntraeger <borntraeger@de.ibm.com> wrote:
> On 30.06.21 15:32, David Hildenbrand wrote:
>> On 22.06.21 22:19, Christian Borntraeger wrote:
>>> This defines 5 new facilities and the new 3931 and 3932 machines.
>>> As before the name is not yet known and we do use gen16a and gen16b.
>>> The new features are part of the full model.
>>>
>>> The default model is still empty (same as z15) and will be added
>>> in a separate patch at a later point in time.
>>>
>>> Also add the dependencies of new facilities and as a fix for z15 add
>>> a dependency from S390_FEAT_VECTOR_PACKED_DECIMAL_ENH to
>>> S390_VECTOR_PACKED_DECIMAL.
>>>
>>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
>>> ---
>>> target/s390x/cpu_features_def.h.inc | 5 +++++
>>> target/s390x/cpu_models.c | 6 ++++++
>>> target/s390x/gen-features.c | 14 ++++++++++++++
>>> 3 files changed, 25 insertions(+)
>>>
>>> diff --git a/target/s390x/cpu_features_def.h.inc b/target/s390x/cpu_features_def.h.inc
>>> index 7db3449e0434..c71caee74411 100644
>>> --- a/target/s390x/cpu_features_def.h.inc
>>> +++ b/target/s390x/cpu_features_def.h.inc
>>> @@ -109,6 +109,11 @@ DEF_FEAT(VECTOR_PACKED_DECIMAL_ENH, "vxpdeh", STFL, 152, "Vector-Packed-Decimal-
>>> DEF_FEAT(MSA_EXT_9, "msa9-base", STFL, 155, "Message-security-assist-extension-9 facility (excluding subfunctions)")
>>> DEF_FEAT(ETOKEN, "etoken", STFL, 156, "Etoken facility")
>>> DEF_FEAT(UNPACK, "unpack", STFL, 161, "Unpack facility")
>>> +DEF_FEAT(NNPA, "nnpa", STFL, 165, "NNPA facility")
>>> +DEF_FEAT(VECTOR_PACKED_DECIMAL_ENH2, "vxpdeh2", STFL, 192, "Vector-Packed-Decimal-Enhancement facility 2")
>>> +DEF_FEAT(BEAR, "bear", STFL, 193, "BEAR-enhancement facility")
>>
>> Usually we use "eh" for enhancement. Which would result in "beareh" or alternatively "beh". But maybe the "enhancement" part is not actually an enhancement, but instead this facility is more like the etoken or unpack facility ...
>
> There was no bear facility (I think it was part of PER3).
> beareh or beh would be fine with me.
>
>>
>>> +DEF_FEAT(RDP, "rdp", STFL, 194, "Reset-DAT-protection facility")
>>> +DEF_FEAT(ACTIVITY, "activity", STFL, 196, "Processor-Activity-Instrumentation facility")
>>
>> Would "pai" be a more appropriate feature name?
>
> pai would be ok for me as well.
>
> Conny, do you want to replace "activity" with "pai" and "bear" with "beareh" in your tree?
I can certainly edit this to a naming everyone agrees with (no strong
opinions from my side).
[Although I rather like large animals in cpu facilities 8)]
next prev parent reply other threads:[~2021-06-30 15:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-22 20:19 [PATCH 0/1] Add features and cpu models Christian Borntraeger
2021-06-22 20:19 ` [PATCH 1/1] s390x/cpumodel: add 3931 and 3932 Christian Borntraeger
2021-06-30 13:32 ` David Hildenbrand
2021-06-30 13:53 ` Christian Borntraeger
2021-06-30 15:32 ` Cornelia Huck [this message]
2021-06-30 15:56 ` Christian Borntraeger
2021-07-01 7:45 ` David Hildenbrand
2021-07-01 8:42 ` Thomas Huth
2021-06-22 20:28 ` [PATCH 0/1] Add features and cpu models no-reply
2021-06-25 9:55 ` Cornelia Huck
2021-07-01 8:43 ` [PATCH fixup] s390x: fixup for "s390x/cpumodel: add 3931 and 3932" Christian Borntraeger
2021-07-01 8:48 ` David Hildenbrand
2021-07-01 11:47 ` Cornelia Huck
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=8735szl66j.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--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).