From: Janosch Frank <frankja@linux.ibm.com>
To: Christoph Schlameuss <schlameuss@linux.ibm.com>, kvm@vger.kernel.org
Cc: linux-s390@vger.kernel.org, linux-kselftest@vger.kernel.org,
Paolo Bonzini <pbonzini@redhat.com>,
Shuah Khan <shuah@kernel.org>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Claudio Imbrenda <imbrenda@linux.ibm.com>,
David Hildenbrand <david@redhat.com>,
Nina Schoetterl-Glausch <nsg@linux.ibm.com>
Subject: Re: [PATCH v5 07/10] selftests: kvm: s390: Add uc_map_unmap VM test case
Date: Tue, 13 Aug 2024 09:21:12 +0200 [thread overview]
Message-ID: <c1af035e-2bc3-4d61-a318-11f2490cb0d5@linux.ibm.com> (raw)
In-Reply-To: <20240807154512.316936-8-schlameuss@linux.ibm.com>
On 8/7/24 5:45 PM, Christoph Schlameuss wrote:
> Add a test case verifying basic running and interaction of ucontrol VMs.
> Fill the segment and page tables for allocated memory and map memory on
> first access.
>
> * uc_map_unmap
> Store and load data to mapped and unmapped memory and use pic segment
> translation handling to map memory on access.
>
> Signed-off-by: Christoph Schlameuss <schlameuss@linux.ibm.com>
> ---
> .../selftests/kvm/s390x/ucontrol_test.c | 167 +++++++++++++++++-
> 1 file changed, 166 insertions(+), 1 deletion(-)
>
[...]
> +static void init_st_pt(FIXTURE_DATA(uc_kvm) * self)
> +{
> + struct kvm_sync_regs *sync_regs = &self->run->s.regs;
> + u64 first_pt_addr, ste, s_addr, pte;
> + struct kvm_run *run = self->run;
> + void *se_addr;
> + int si, pi;
> + u64 *phd;
> +
> + /* set PASCE addr */
> + self->pgd = self->base_gpa + SZ_1M;
> + phd = gpa2hva(self, self->pgd);
> + memset(phd, 0xff, VM_MEM_TABLE_SIZE);
> +
> + first_pt_addr = self->pgd + (VM_MEM_TABLE_SIZE * VM_MEM_MAX_M);
> + /* for each segment in the VM */
> + for (si = 0; si < VM_MEM_MAX_M; si++) {
> + /* build segment table entry (ste) */
> + ste = (first_pt_addr + (VM_MEM_TABLE_SIZE * si)) & ~0x7fful;
> + /* store ste in st */
> + phd[si] = ste;
> +
> + se_addr = gpa2hva(self, phd[si]);
> + s_addr = self->base_gpa + (si * SZ_1M);
> + memset(se_addr, 0xff, VM_MEM_TABLE_SIZE);
> + /* for each page in the segment (VM) */
> + for (pi = 0; pi < (SZ_1M / PAGE_SIZE); pi++) {
> + /* build page table entry (pte) */
> + pte = (s_addr + (pi * PAGE_SIZE)) & ~0xffful;
> + /* store pte in pt */
> + ((u64 *)se_addr)[pi] = pte;
> + }
> + }
> + pr_debug("segment table entry %p (0x%lx) --> %p\n",
> + phd, phd[0], gpa2hva(self, (phd[0] & ~0x7fful)));
> + print_hex_bytes("st", (u64)phd, 64);
> + print_hex_bytes("pt", (u64)gpa2hva(self, phd[0]), 128);
> +
> + /* PASCE TT=00 for segment table */
> + sync_regs->crs[1] = self->pgd | 0x3;
> + run->kvm_dirty_regs |= KVM_SYNC_CRS;
> +}
Having a closer look at this I don't understand why we need to setup DAT
in the guest. Also, the guest's memory easily fits in a couple of
segment entries so you could set the table length TL in the ASCE to one
page instead of 4.
next prev parent reply other threads:[~2024-08-13 7:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-07 15:45 [PATCH v5 00/10] selftests: kvm: s390: Add s390x ucontrol selftests Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 01/10] selftests: kvm: s390: Define page sizes in shared header Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 02/10] selftests: kvm: s390: Add kvm_s390_sie_block definition for userspace tests Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 03/10] selftests: kvm: s390: Add s390x ucontrol test suite with hpage test Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 04/10] selftests: kvm: s390: Add test fixture and simple VM setup tests Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 05/10] selftests: kvm: s390: Add debug print functions Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 06/10] selftests: kvm: s390: Add VM run test case Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 07/10] selftests: kvm: s390: Add uc_map_unmap VM " Christoph Schlameuss
2024-08-13 7:21 ` Janosch Frank [this message]
2024-08-13 10:57 ` Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 08/10] selftests: kvm: s390: Add uc_skey " Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 09/10] selftests: kvm: s390: Verify reject memory region operations for ucontrol VMs Christoph Schlameuss
2024-08-07 15:45 ` [PATCH v5 10/10] s390: Enable KVM_S390_UCONTROL config in debug_defconfig Christoph Schlameuss
2024-08-13 11:54 ` [PATCH v5 00/10] selftests: kvm: s390: Add s390x ucontrol selftests 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=c1af035e-2bc3-4d61-a318-11f2490cb0d5@linux.ibm.com \
--to=frankja@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=nsg@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=schlameuss@linux.ibm.com \
--cc=shuah@kernel.org \
/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