From: Nico Boehr <nrb@linux.ibm.com>
To: frankja@linux.ibm.com, imbrenda@linux.ibm.com, thuth@redhat.com
Cc: kvm@vger.kernel.org, linux-s390@vger.kernel.org
Subject: [kvm-unit-tests PATCH v2 3/3] s390x: mvpg-sie: fix virtual-physical address confusion
Date: Mon, 6 Nov 2023 18:08:02 +0100 [thread overview]
Message-ID: <20231106170849.1184162-4-nrb@linux.ibm.com> (raw)
In-Reply-To: <20231106170849.1184162-1-nrb@linux.ibm.com>
The addresses reported for the partial execution of mvpg instruction are
physical addresses. Now that MSO is a virtual address, we can't simply
compare the PEI fields in the sie block with MSO, but need to do an
additional translation step.
Add the necessary virtual-physical translations and expose the
virt_to_pte_phys() function in mmu.h which is useful for this kind of
translation.
Signed-off-by: Nico Boehr <nrb@linux.ibm.com>
---
lib/s390x/mmu.h | 2 ++
s390x/mvpg-sie.c | 15 +++++++++++----
2 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/lib/s390x/mmu.h b/lib/s390x/mmu.h
index dadc2e600f9a..e9e837236603 100644
--- a/lib/s390x/mmu.h
+++ b/lib/s390x/mmu.h
@@ -95,4 +95,6 @@ static inline void unprotect_page(void *vaddr, unsigned long prot)
void *get_dat_entry(pgd_t *pgtable, void *vaddr, enum pgt_level level);
+phys_addr_t virt_to_pte_phys(pgd_t *pgtable, void *vaddr);
+
#endif /* _ASMS390X_MMU_H_ */
diff --git a/s390x/mvpg-sie.c b/s390x/mvpg-sie.c
index 99f4859bc2df..effb5eab2c0e 100644
--- a/s390x/mvpg-sie.c
+++ b/s390x/mvpg-sie.c
@@ -23,7 +23,9 @@
static struct vm vm;
static uint8_t *src;
+static phys_addr_t src_phys;
static uint8_t *dst;
+static phys_addr_t dst_phys;
static uint8_t *cmp;
static void test_mvpg_pei(void)
@@ -38,8 +40,8 @@ static void test_mvpg_pei(void)
protect_page(src, PAGE_ENTRY_I);
sie(&vm);
report(vm.sblk->icptcode == ICPT_PARTEXEC, "Partial execution");
- report((uintptr_t)**pei_src == (uintptr_t)src + PAGE_ENTRY_I, "PEI_SRC correct");
- report((uintptr_t)**pei_dst == (uintptr_t)dst, "PEI_DST correct");
+ report((uintptr_t)**pei_src == (uintptr_t)src_phys + PAGE_ENTRY_I, "PEI_SRC correct");
+ report((uintptr_t)**pei_dst == (uintptr_t)dst_phys, "PEI_DST correct");
unprotect_page(src, PAGE_ENTRY_I);
report(!memcmp(cmp, dst, PAGE_SIZE), "Destination intact");
/*
@@ -60,8 +62,8 @@ static void test_mvpg_pei(void)
protect_page(dst, PAGE_ENTRY_I);
sie(&vm);
report(vm.sblk->icptcode == ICPT_PARTEXEC, "Partial execution");
- report((uintptr_t)**pei_src == (uintptr_t)src, "PEI_SRC correct");
- report((uintptr_t)**pei_dst == (uintptr_t)dst + PAGE_ENTRY_I, "PEI_DST correct");
+ report((uintptr_t)**pei_src == (uintptr_t)src_phys, "PEI_SRC correct");
+ report((uintptr_t)**pei_dst == (uintptr_t)dst_phys + PAGE_ENTRY_I, "PEI_DST correct");
/* Needed for the memcmp and general cleanup */
unprotect_page(dst, PAGE_ENTRY_I);
report(!memcmp(cmp, dst, PAGE_SIZE), "Destination intact");
@@ -82,8 +84,10 @@ static void setup_guest(void)
{
extern const char SNIPPET_NAME_START(c, mvpg_snippet)[];
extern const char SNIPPET_NAME_END(c, mvpg_snippet)[];
+ pgd_t *root;
setup_vm();
+ root = (pgd_t *)(stctg(1) & PAGE_MASK);
snippet_setup_guest(&vm, false);
snippet_init(&vm, SNIPPET_NAME_START(c, mvpg_snippet),
@@ -94,6 +98,9 @@ static void setup_guest(void)
src = (uint8_t *) vm.sblk->mso + PAGE_SIZE * 6;
dst = (uint8_t *) vm.sblk->mso + PAGE_SIZE * 5;
+ src_phys = virt_to_pte_phys(root, src);
+ dst_phys = virt_to_pte_phys(root, dst);
+
cmp = alloc_page();
memset(cmp, 0, PAGE_SIZE);
}
--
2.41.0
next prev parent reply other threads:[~2023-11-06 17:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 17:07 [kvm-unit-tests PATCH v2 0/3] s390x: Align SIE tests to 2GB Nico Boehr
2023-11-06 17:08 ` [kvm-unit-tests PATCH v2 1/3] s390x: spec_ex-sie: refactor to use snippet API Nico Boehr
2023-11-06 17:08 ` [kvm-unit-tests PATCH v2 2/3] s390x: sie: ensure guests are aligned to 2GB Nico Boehr
2023-11-07 12:26 ` Claudio Imbrenda
2023-11-06 17:08 ` Nico Boehr [this message]
2023-11-07 12:54 ` [kvm-unit-tests PATCH v2 3/3] s390x: mvpg-sie: fix virtual-physical address confusion Claudio Imbrenda
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=20231106170849.1184162-4-nrb@linux.ibm.com \
--to=nrb@linux.ibm.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