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 1/4] selftests: kvm: s390: Add uc_map_unmap VM test case
Date: Tue, 17 Sep 2024 13:50:09 +0200 [thread overview]
Message-ID: <5f247db9-5d63-40d4-82e8-4ade9be714ad@linux.ibm.com> (raw)
In-Reply-To: <20240917064456.210839-2-schlameuss@linux.ibm.com>
On 9/17/24 8:44 AM, 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>
>
Reviewed-by: Janosch Frank <frankja@linux.ibm.com>
next prev parent reply other threads:[~2024-09-17 11:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-17 6:44 [PATCH v4 0/4] selftests: kvm: s390: Add ucontrol memory selftests Christoph Schlameuss
2024-09-17 6:44 ` [PATCH v4 1/4] selftests: kvm: s390: Add uc_map_unmap VM test case Christoph Schlameuss
2024-09-17 11:50 ` Janosch Frank [this message]
2024-09-17 6:44 ` [PATCH v4 2/4] selftests: kvm: s390: Add uc_skey " Christoph Schlameuss
2024-09-17 14:13 ` Janosch Frank
2024-09-17 6:44 ` [PATCH v4 3/4] selftests: kvm: s390: Verify reject memory region operations for ucontrol VMs Christoph Schlameuss
2024-09-17 6:44 ` [PATCH v4 4/4] fixup! selftests: kvm: s390: Add VM run test case Christoph Schlameuss
2024-09-17 14:20 ` 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=5f247db9-5d63-40d4-82e8-4ade9be714ad@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