From: Janosch Frank <frankja@linux.ibm.com>
To: kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, imbrenda@linux.ibm.com,
david@redhat.com, thuth@redhat.com, cohuck@redhat.com
Subject: [kvm-unit-tests PATCH 2/8] lib: s390x: Add 0x3d, 0x3e and 0x3f PGM constants
Date: Fri, 13 Aug 2021 07:36:09 +0000 [thread overview]
Message-ID: <20210813073615.32837-3-frankja@linux.ibm.com> (raw)
In-Reply-To: <20210813073615.32837-1-frankja@linux.ibm.com>
For UV and format 4 SIE tests we need to handle the following PGM exceptions:
0x3d Secure Storage Access (non-secure CPU accesses secure storage)
0x3e Non-Secure Storage Access (secure CPU accesses non-secure storage)
0x3f Mapping of secure guest is wrong
Signed-off-by: Janosch Frank <frankja@linux.ibm.com>
---
lib/s390x/asm/arch_def.h | 3 +++
lib/s390x/interrupt.c | 3 +++
2 files changed, 6 insertions(+)
diff --git a/lib/s390x/asm/arch_def.h b/lib/s390x/asm/arch_def.h
index 15cf7d48..4ca02c1d 100644
--- a/lib/s390x/asm/arch_def.h
+++ b/lib/s390x/asm/arch_def.h
@@ -177,6 +177,9 @@ _Static_assert(sizeof(struct lowcore) == 0x1900, "Lowcore size");
#define PGM_INT_CODE_REGION_FIRST_TRANS 0x39
#define PGM_INT_CODE_REGION_SECOND_TRANS 0x3a
#define PGM_INT_CODE_REGION_THIRD_TRANS 0x3b
+#define PGM_INT_CODE_SECURE_STOR_ACCESS 0x3d
+#define PGM_INT_CODE_NON_SECURE_STOR_ACCESS 0x3e
+#define PGM_INT_CODE_SECURE_STOR_VIOLATION 0x3f
#define PGM_INT_CODE_MONITOR_EVENT 0x40
#define PGM_INT_CODE_PER 0x80
#define PGM_INT_CODE_CRYPTO_OPERATION 0x119
diff --git a/lib/s390x/interrupt.c b/lib/s390x/interrupt.c
index 785b7355..01ded49d 100644
--- a/lib/s390x/interrupt.c
+++ b/lib/s390x/interrupt.c
@@ -115,6 +115,9 @@ static void fixup_pgm_int(struct stack_frame_int *stack)
case PGM_INT_CODE_REGION_THIRD_TRANS:
case PGM_INT_CODE_PER:
case PGM_INT_CODE_CRYPTO_OPERATION:
+ case PGM_INT_CODE_SECURE_STOR_ACCESS:
+ case PGM_INT_CODE_NON_SECURE_STOR_ACCESS:
+ case PGM_INT_CODE_SECURE_STOR_VIOLATION:
/* The interrupt was nullified, the old PSW points at the
* responsible instruction. Forward the PSW so we don't loop.
*/
--
2.30.2
next prev parent reply other threads:[~2021-08-13 7:37 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-13 7:36 [kvm-unit-tests PATCH 0/8] s390x: Cleanup and maintenance Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 1/8] s390x: lib: Extend bitops Janosch Frank
2021-08-13 8:32 ` Claudio Imbrenda
2021-08-13 11:31 ` Janosch Frank
2021-08-18 8:20 ` Thomas Huth
2021-08-18 8:39 ` Janosch Frank
2021-08-18 8:57 ` Thomas Huth
2021-08-13 7:36 ` Janosch Frank [this message]
2021-08-13 8:20 ` [kvm-unit-tests PATCH 2/8] lib: s390x: Add 0x3d, 0x3e and 0x3f PGM constants Claudio Imbrenda
2021-08-13 7:36 ` [kvm-unit-tests PATCH 3/8] lib: s390x: Print addressing related exception information Janosch Frank
2021-08-13 8:40 ` Claudio Imbrenda
2021-08-13 11:34 ` Janosch Frank
2021-08-18 9:12 ` Thomas Huth
2021-08-18 9:29 ` Claudio Imbrenda
2021-08-18 9:53 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 4/8] lib: s390x: Start using bitops instead of magic constants Janosch Frank
2021-08-13 8:41 ` Claudio Imbrenda
2021-08-18 9:24 ` Thomas Huth
2021-08-13 7:36 ` [kvm-unit-tests PATCH 5/8] s390x: uv-host: Explain why we set up the home space and remove the space change Janosch Frank
2021-08-13 8:45 ` Claudio Imbrenda
2021-08-13 13:14 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 6/8] lib: s390x: Add PSW_MASK_64 Janosch Frank
2021-08-13 8:46 ` Claudio Imbrenda
2021-08-18 9:28 ` Thomas Huth
2021-08-13 7:36 ` [kvm-unit-tests PATCH 7/8] lib: s390x: Control register constant cleanup Janosch Frank
2021-08-13 8:49 ` Claudio Imbrenda
2021-08-13 9:09 ` Janosch Frank
2021-08-13 7:36 ` [kvm-unit-tests PATCH 8/8] lib: s390x: uv: Add rc 0x100 query error handling Janosch Frank
2021-08-13 8:50 ` Claudio Imbrenda
2021-08-18 9:30 ` Thomas Huth
2021-08-18 9:57 ` 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=20210813073615.32837-3-frankja@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-s390@vger.kernel.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).