From: Harald Freudenberger <freude@linux.ibm.com>
To: richard.henderson@linaro.org, iii@linux.ibm.com,
david@kernel.org, thuth@redhat.com, berrange@redhat.com
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
linux-s390@vger.kernel.org, dengler@linux.ibm.com,
borntraeger@linux.ibm.com, fcallies@linux.ibm.com,
cohuck@redhat.com
Subject: [PATCH v15 01/20] target/s390x: Fix missing privileged flag at PCKMO instruction
Date: Tue, 18 Aug 2026 18:18:05 +0200 [thread overview]
Message-ID: <20260818161824.100746-2-freude@linux.ibm.com> (raw)
In-Reply-To: <20260818161824.100746-1-freude@linux.ibm.com>
The CPACF instruction PCKMO is a privileged instruction. So set the
IF_PRIV flag in insn-data.h.inc to reflect this.
Signed-off-by: Harald Freudenberger <freude@linux.ibm.com>
Reviewed-by: Ilya Leoshkevich <iii@linux.ibm.com>
---
target/s390x/tcg/insn-data.h.inc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/target/s390x/tcg/insn-data.h.inc b/target/s390x/tcg/insn-data.h.inc
index 1ea72248a6..b2e402216b 100644
--- a/target/s390x/tcg/insn-data.h.inc
+++ b/target/s390x/tcg/insn-data.h.inc
@@ -1007,7 +1007,7 @@
/* MSA Instructions */
D(0xb91e, KMAC, RRE, MSA, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_KMAC)
- D(0xb928, PCKMO, RRE, MSA3, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_PCKMO)
+ E(0xb928, PCKMO, RRE, MSA3, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_PCKMO, IF_PRIV)
D(0xb92a, KMF, RRE, MSA4, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_KMF)
D(0xb92b, KMO, RRE, MSA4, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_KMO)
D(0xb92c, PCC, RRE, MSA4, 0, 0, 0, 0, msa, 0, S390_FEAT_TYPE_PCC)
--
2.43.0
next prev parent reply other threads:[~2026-08-18 16:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 16:18 [PATCH v15 00/20] Extend qemu CPACF support Harald Freudenberger
2026-08-18 16:18 ` Harald Freudenberger [this message]
2026-08-18 16:18 ` [PATCH v15 02/20] target/s390x: Rework s390 cpacf implementations Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 03/20] target/s390x: Move cpacf sha512 code into a new file Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 04/20] target/s390x: Support cpacf sha256 Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 05/20] target/s390x: Add helper functions for copy memory to and from guest Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 06/20] target/s390x: Adjust addressing mode checks for sha512 and sha256 Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 07/20] crypto: Add aes-helpers file to support some AES modes Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 08/20] target/s390x: Support AES ECB for cpacf km instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 09/20] target/s390x: Support AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 10/20] target/s390x: Support AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 11/20] target/s390x: Minimal AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 12/20] target/s390x: Support AES XTS for cpacf km instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 13/20] target/s390x: Base support for cpacf protected keys and pckmo Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 14/20] target/s390x: Support protected key AES ECB for cpacf km instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 15/20] target/s390x: Support protected key AES CBC for cpacf kmc instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 16/20] target/s390x: Support protected key AES CTR for cpacf kmctr instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 17/20] target/s390x: Minimal protected key AES XTS support for cpacf pcc instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 18/20] target/s390x: Support protected key AES XTS for cpacf km instruction Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 19/20] docs/s390: Document CPACF instructions support Harald Freudenberger
2026-08-18 16:18 ` [PATCH v15 20/20] tests/tcg/s390x: Add tests for CPACF instructions Harald Freudenberger
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=20260818161824.100746-2-freude@linux.ibm.com \
--to=freude@linux.ibm.com \
--cc=berrange@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@kernel.org \
--cc=dengler@linux.ibm.com \
--cc=fcallies@linux.ibm.com \
--cc=iii@linux.ibm.com \
--cc=linux-s390@vger.kernel.org \
--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