public inbox for linux-s390@vger.kernel.org
 help / color / mirror / Atom feed
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 v4 07/10] selftests: kvm: s390: Add uc_map_unmap VM test case
Date: Tue, 6 Aug 2024 15:13:34 +0200	[thread overview]
Message-ID: <dc515da5-6b22-4e15-acfe-d7d0849d16a6@linux.ibm.com> (raw)
In-Reply-To: <20240802155913.261891-8-schlameuss@linux.ibm.com>

On 8/2/24 5:59 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       | 165 +++++++++++++++++-
>   1 file changed, 164 insertions(+), 1 deletion(-)
> 
> diff --git a/tools/testing/selftests/kvm/s390x/ucontrol_test.c b/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> index 030c59010fe1..72ad30fbe4ac 100644
> --- a/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> +++ b/tools/testing/selftests/kvm/s390x/ucontrol_test.c
> @@ -16,7 +16,13 @@
>   #include <linux/capability.h>
>   #include <linux/sizes.h>

[...]

> +#define VM_MEM_MAX (VM_MEM_SIZE + VM_MEM_EXT_SIZE)

You defined this but never use it.
Instead you're still adding up VM_MEM_SIZE and VM_MEM_EXT_SIZE.

> +
> +#define PAGES_PER_SEGMENT 4

You mean pages per segment table?

[...]

> +/* initialize segment and page tables for uc_kvm tests */
> +static void init_st_pt(FIXTURE_DATA(uc_kvm) * self)
> +{
> +	struct kvm_sync_regs *sync_regs = &self->run->s.regs;
> +	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, PAGES_PER_SEGMENT * PAGE_SIZE);
> +
> +	for (si = 0; si < ((VM_MEM_SIZE + VM_MEM_EXT_SIZE) / SZ_1M); si++) {
> +		/* create ste */
> +		phd[si] = (self->pgd
> +			+ (PAGES_PER_SEGMENT * PAGE_SIZE
> +				* ((VM_MEM_SIZE + VM_MEM_EXT_SIZE) / SZ_1M))
> +			+ (PAGES_PER_SEGMENT * PAGE_SIZE * si)) & ~0x7fful;
> +		se_addr = gpa2hva(self, phd[si]);
> +		memset(se_addr, 0xff, PAGES_PER_SEGMENT * PAGE_SIZE);
> +		for (pi = 0; pi < (SZ_1M / PAGE_SIZE); pi++) {
> +			/* create pte */
> +			((u64 *)se_addr)[pi] = (self->base_gpa
> +				+ (si * SZ_1M) + (pi * PAGE_SIZE)) & ~0xffful;
> +		}

That's barely readable, can you split that into functions or make it 
more readable in some other way?

> +	}
> +	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);
> +	print_hex_bytes("pt+", (u64)
> +			gpa2hva(self, phd[0] + (PAGES_PER_SEGMENT * PAGE_SIZE
> +			* ((VM_MEM_SIZE + VM_MEM_EXT_SIZE) / SZ_1M)) - 0x64), 128);
> +
> +	/* PASCE TT=00 for segment table */
> +	sync_regs->crs[1] = self->pgd | 0x3;
> +	run->kvm_dirty_regs |= KVM_SYNC_CRS;
> +}
> +


  reply	other threads:[~2024-08-06 13:13 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02 15:59 [PATCH v4 00/10] selftests: kvm: s390: Add s390x ucontrol selftests Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 01/10] selftests: kvm: s390: Define page sizes in shared header Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 02/10] selftests: kvm: s390: Add kvm_s390_sie_block definition for userspace tests Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 03/10] selftests: kvm: s390: Add s390x ucontrol test suite with hpage test Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 04/10] selftests: kvm: s390: Add test fixture and simple VM setup tests Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 05/10] selftests: kvm: s390: Add debug print functions Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 06/10] selftests: kvm: s390: Add VM run test case Christoph Schlameuss
2024-08-06 13:02   ` Janosch Frank
2024-08-02 15:59 ` [PATCH v4 07/10] selftests: kvm: s390: Add uc_map_unmap VM " Christoph Schlameuss
2024-08-06 13:13   ` Janosch Frank [this message]
2024-08-06 14:44     ` Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 08/10] selftests: kvm: s390: Add uc_skey " Christoph Schlameuss
2024-08-06 13:39   ` Janosch Frank
2024-08-07 11:02     ` Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 09/10] selftests: kvm: s390: Verify reject memory region operations for ucontrol VMs Christoph Schlameuss
2024-08-02 15:59 ` [PATCH v4 10/10] s390: Enable KVM_S390_UCONTROL config in debug_defconfig Christoph Schlameuss

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=dc515da5-6b22-4e15-acfe-d7d0849d16a6@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