qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hendrik Brueckner <brueckner@linux.ibm.com>
To: Janosch Frank <frankja@linux.ibm.com>
Cc: Hendrik Brueckner <brueckner@linux.ibm.com>,
	qemu-devel@nongnu.org, qemu-s390x@nongnu.org, thuth@redhat.com,
	nsg@linux.ibm.com, mimu@linux.ibm.com, borntraeger@linux.ibm.com
Subject: Re: [RFC PATCH v2 02/15] s390x/cpumodel: add msa11 subfunctions
Date: Mon, 9 Dec 2024 16:29:27 +0100	[thread overview]
Message-ID: <Z1cM1y84HNdJnvon@linux.ibm.com> (raw)
In-Reply-To: <b9425123-d388-4a60-975c-98e14743ae9d@linux.ibm.com>

On Mon, Dec 09, 2024 at 04:04:19PM +0100, Janosch Frank wrote:
> On 12/6/24 1:27 PM, Hendrik Brueckner wrote:
> > MSA11 introduces new HMAC subfunctions.
> > 
> > Signed-off-by: Hendrik Brueckner <brueckner@linux.ibm.com>
> > Reviewed-by: Christian Borntraeger <borntraeger@linux.ibm.com>
> > ---
> >   target/s390x/cpu_features.c         |  2 ++
> >   target/s390x/cpu_features_def.h.inc | 10 ++++++++++
> >   target/s390x/cpu_models.c           |  8 ++++++++
> >   target/s390x/gen-features.c         | 24 ++++++++++++++++++++++++
> >   4 files changed, 44 insertions(+)
> [...]
> >   /* Features exposed via the KMC instruction. */
> >   DEF_FEAT(KMC_DEA, "kmc-dea", KMC, 1, "KMC DEA")
> > @@ -275,6 +283,8 @@ DEF_FEAT(PCKMO_ECC_P384, "pckmo-ecc-p384", PCKMO, 33, "PCKMO Encrypt-ECC-P384-Ke
> >   DEF_FEAT(PCKMO_ECC_P521, "pckmo-ecc-p521", PCKMO, 34, "PCKMO Encrypt-ECC-P521-Key")
> >   DEF_FEAT(PCKMO_ECC_ED25519, "pckmo-ecc-ed25519", PCKMO, 40 , "PCKMO Encrypt-ECC-Ed25519-Key")
> >   DEF_FEAT(PCKMO_ECC_ED448, "pckmo-ecc-ed448", PCKMO, 41 , "PCKMO Encrypt-ECC-Ed448-Key")
> > +DEF_FEAT(PCKMO_HMAC_512, "pckmo-hmac-512", PCKMO, 118, "PCKMO Encrypt-HMAC-512-Key")
> > +DEF_FEAT(PCKMO_HMAC_1024, "pckmo-hmac-1024", PCKMO, 122, "PCKMO Encrypt-HMAC-1024-Key")
> 
> It seems like we never did MSAx prereq checks for PCKMO like we do for the
> other instructions. Don't we need to check for MSA3 for these features too?
> 
> I see no code that puts EXT_11 and EXT_11_PCKMO in a group where we could
> piggyback on the EXT_11 check for MSA3. What am I missing?

Similar to my other comment. EXT_11 does not have an STFLE bit and, hence,
no feature definition. That's why each introduced subfunc requires MSA3
(for which there is STFLE bit).

The check_consistencies functions works on feature definitions, not on the
feature group definitions.

Hope this helps.



  reply	other threads:[~2024-12-09 15:30 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-06 12:27 [RFC PATCH v2 00/15] KVM: s390: CPU model for gen17 Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 01/15] s390x/cpumodel: add msa10 subfunctions Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 02/15] s390x/cpumodel: add msa11 subfunctions Hendrik Brueckner
2024-12-09 15:04   ` Janosch Frank
2024-12-09 15:29     ` Hendrik Brueckner [this message]
2024-12-10 11:52       ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 03/15] s390x/cpumodel: add msa12 changes Hendrik Brueckner
2024-12-09 14:48   ` Janosch Frank
2024-12-09 15:24     ` Hendrik Brueckner
2024-12-09 15:45       ` Janosch Frank
2024-12-09 15:54         ` Hendrik Brueckner
2024-12-10  7:45           ` Janosch Frank
2024-12-10 12:51             ` [RFC PATCH] s390x/cpumodel: add MSA 12 consistency checks Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 04/15] s390x/cpumodel: add msa13 subfunctions Hendrik Brueckner
2024-12-09 14:34   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 05/15] s390x/cpumodel: Add ptff Query Time-Stamp Event (QTSE) support Hendrik Brueckner
2024-12-10 12:41   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 06/15] linux-headers: Update to Linux 6.13-rc1 Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 07/15] s390x/cpumodel: add Concurrent-functions facility support Hendrik Brueckner
2024-12-10 11:47   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 08/15] s390x/cpumodel: add Vector Enhancements facility 3 Hendrik Brueckner
2024-12-10 11:42   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 09/15] s390x/cpumodel: add Miscellaneous-Instruction-Extensions Facility 4 Hendrik Brueckner
2024-12-10 11:44   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 10/15] s390x/cpumodel: add Vector-Packed-Decimal-Enhancement facility 3 Hendrik Brueckner
2024-12-10 11:43   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 11/15] s390x/cpumodel: add Ineffective-nonconstrained-transaction facility Hendrik Brueckner
2024-12-10 11:49   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 12/15] s390x/cpumodel: Add Sequential-Instruction-Fetching facility Hendrik Brueckner
2024-12-10 11:50   ` Janosch Frank
2024-12-06 12:27 ` [RFC PATCH v2 13/15] s390x/cpumodel: correct PLO feature wording Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 14/15] s390x/cpumodel: Add PLO-extension facility Hendrik Brueckner
2024-12-06 12:27 ` [RFC PATCH v2 15/15] s390x/cpumodel: gen17 model Hendrik Brueckner
2024-12-06 14:14 ` [RFC PATCH v2 00/15] KVM: s390: CPU model for gen17 Richard Henderson
2024-12-09 10:14   ` Janosch Frank

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=Z1cM1y84HNdJnvon@linux.ibm.com \
    --to=brueckner@linux.ibm.com \
    --cc=borntraeger@linux.ibm.com \
    --cc=frankja@linux.ibm.com \
    --cc=mimu@linux.ibm.com \
    --cc=nsg@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.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).