From: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Janosch Frank <frankja@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>
Cc: Janis Schoetterl-Glausch <scgl@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [kvm-unit-tests PATCH] s390x/intercept: Test invalid prefix argument to SET PREFIX
Date: Mon, 27 Jun 2022 14:43:56 +0200 [thread overview]
Message-ID: <20220627124356.2033539-1-scgl@linux.ibm.com> (raw)
According to the architecture, SET PREFIX must try to access the new
prefix area and recognize an addressing exception if the area is not
accessible.
Test that the exception occurs when we try to set a prefix higher
than the available memory.
Signed-off-by: Janis Schoetterl-Glausch <scgl@linux.ibm.com>
---
s390x/intercept.c | 14 ++++++++++++++
1 file changed, 14 insertions(+)
diff --git a/s390x/intercept.c b/s390x/intercept.c
index 86e57e11..0b90e588 100644
--- a/s390x/intercept.c
+++ b/s390x/intercept.c
@@ -74,6 +74,20 @@ static void test_spx(void)
expect_pgm_int();
asm volatile(" spx 0(%0) " : : "r"(-8L));
check_pgm_int_code(PGM_INT_CODE_ADDRESSING);
+
+ new_prefix = get_ram_size() & 0x7fffe000;
+ if (get_ram_size() - new_prefix < 2 * PAGE_SIZE) {
+ expect_pgm_int();
+ asm volatile("spx %0 " : : "Q"(new_prefix));
+ check_pgm_int_code(PGM_INT_CODE_ADDRESSING);
+
+ /*
+ * Cannot test inaccessibility of the second page the same way.
+ * If we try to use the last page as first half of the prefix
+ * area and our ram size is a multiple of 8k, after SPX aligns
+ * the address to 8k we have a completely accessible area.
+ */
+ }
}
/* Test the STORE CPU ADDRESS instruction */
base-commit: 110c69492b53f0070e1bbce986fb635e72a423b4
--
2.36.1
next reply other threads:[~2022-06-27 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 12:43 Janis Schoetterl-Glausch [this message]
2022-06-27 12:52 ` [kvm-unit-tests PATCH] s390x/intercept: Test invalid prefix argument to SET PREFIX Claudio Imbrenda
2022-06-27 12:58 ` Janis Schoetterl-Glausch
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=20220627124356.2033539-1-scgl@linux.ibm.com \
--to=scgl@linux.ibm.com \
--cc=david@redhat.com \
--cc=frankja@linux.ibm.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