From: Shuah Khan <skhan@linuxfoundation.org>
To: Vishal Annapurve <vannapurve@google.com>,
x86@kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Cc: pbonzini@redhat.com, vkuznets@redhat.com, wanpengli@tencent.com,
jmattson@google.com, joro@8bytes.org, tglx@linutronix.de,
mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
hpa@zytor.com, shauh@kernel.org, yang.zhong@intel.com,
drjones@redhat.com, ricarkol@google.com, aaronlewis@google.com,
wei.w.wang@intel.com, kirill.shutemov@linux.intel.com,
corbet@lwn.net, hughd@google.com, jlayton@kernel.org,
bfields@fieldses.org, akpm@linux-foundation.org,
chao.p.peng@linux.intel.com, yu.c.zhang@linux.intel.com,
jun.nakajima@intel.com, dave.hansen@intel.com,
michael.roth@amd.com, qperret@google.com, steven.price@arm.com,
ak@linux.intel.com, david@redhat.com, luto@kernel.org,
vbabka@suse.cz, marcorr@google.com, erdemaktas@google.com,
pgonda@google.com, nikunj@amd.com, seanjc@google.com,
diviness@google.com, Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [RFC V2 PATCH 3/8] selftests: kvm: priv_memfd_test: Add support for memory conversion
Date: Thu, 12 May 2022 11:40:57 -0600 [thread overview]
Message-ID: <934a07be-ce72-7916-5614-e78af8293b5c@linuxfoundation.org> (raw)
In-Reply-To: <20220511000811.384766-4-vannapurve@google.com>
On 5/10/22 6:08 PM, Vishal Annapurve wrote:
> Add handling of explicit private/shared memory conversion using
> KVM_HC_MAP_GPA_RANGE and implicit memory conversion by handling
> KVM_EXIT_MEMORY_ERROR.
>
> Signed-off-by: Vishal Annapurve <vannapurve@google.com>
> ---
> tools/testing/selftests/kvm/priv_memfd_test.c | 87 +++++++++++++++++++
> 1 file changed, 87 insertions(+)
>
> diff --git a/tools/testing/selftests/kvm/priv_memfd_test.c b/tools/testing/selftests/kvm/priv_memfd_test.c
> index bbb58c62e186..55e24c893b07 100644
> --- a/tools/testing/selftests/kvm/priv_memfd_test.c
> +++ b/tools/testing/selftests/kvm/priv_memfd_test.c
> @@ -155,6 +155,83 @@ static struct test_run_helper priv_memfd_testsuite[] = {
> },
> };
>
> +static void handle_vm_exit_hypercall(struct kvm_run *run,
> + uint32_t test_id)
> +{
> + uint64_t gpa, npages, attrs;
> + int priv_memfd =
> + priv_memfd_testsuite[test_id].priv_memfd;
Do you need this on a separate line? Doesn't looks like it will exceed
the limit with the tab?
> + int ret;
> + int fallocate_mode;
> +
> + if (run->hypercall.nr != KVM_HC_MAP_GPA_RANGE) {
> + TEST_FAIL("Unhandled Hypercall %lld\n",
> + run->hypercall.nr);
Is this considered test fail or skip because of unmet dependency?
Also do you need run->hypercall.nr os a separate line?
> + }
> +
> + gpa = run->hypercall.args[0];
> + npages = run->hypercall.args[1];
> + attrs = run->hypercall.args[2];
> +
> + if ((gpa < TEST_MEM_GPA) || ((gpa +
> + (npages << MIN_PAGE_SHIFT)) > TEST_MEM_END)) {
> + TEST_FAIL("Unhandled gpa 0x%lx npages %ld\n",
> + gpa, npages);
Same question here about gpa, npages on a separate line? Also
align it with the previous line for readability.
TEST_FAIL("Unhandled gpa 0x%lx npages %ld\n",
gpa, npages);
> + }
> +
> + if (attrs & KVM_MAP_GPA_RANGE_ENCRYPTED)
> + fallocate_mode = 0;
> + else {
> + fallocate_mode = (FALLOC_FL_PUNCH_HOLE |
> + FALLOC_FL_KEEP_SIZE);
> + }
> + pr_info("Converting off 0x%lx pages 0x%lx to %s\n",
> + (gpa - TEST_MEM_GPA), npages,
> + fallocate_mode ?
> + "shared" : "private");
> + ret = fallocate(priv_memfd, fallocate_mode,
> + (gpa - TEST_MEM_GPA),
> + npages << MIN_PAGE_SHIFT);
> + TEST_ASSERT(ret != -1,
> + "fallocate failed in hc handling");
> + run->hypercall.ret = 0;
> +}
> +
> +static void handle_vm_exit_memory_error(struct kvm_run *run,
> + uint32_t test_id)
> +{
> + uint64_t gpa, size, flags;
> + int ret;
> + int priv_memfd =
> + priv_memfd_testsuite[test_id].priv_memfd;
> + int fallocate_mode;
> +
> + gpa = run->memory.gpa;
> + size = run->memory.size;
> + flags = run->memory.flags;
> +
> + if ((gpa < TEST_MEM_GPA) || ((gpa + size)
> + > TEST_MEM_END)) {
> + TEST_FAIL("Unhandled gpa 0x%lx size 0x%lx\n",
> + gpa, size);
> + }
> +
> + if (flags & KVM_MEMORY_EXIT_FLAG_PRIVATE)
> + fallocate_mode = 0;
> + else {
> + fallocate_mode = (FALLOC_FL_PUNCH_HOLE |
> + FALLOC_FL_KEEP_SIZE);
> + }
> + pr_info("Converting off 0x%lx size 0x%lx to %s\n",
> + (gpa - TEST_MEM_GPA), size,
> + fallocate_mode ?
> + "shared" : "private");
> + ret = fallocate(priv_memfd, fallocate_mode,
> + (gpa - TEST_MEM_GPA), size);
> + TEST_ASSERT(ret != -1,
> + "fallocate failed in memory error handling");
> +}
> +
> static void vcpu_work(struct kvm_vm *vm, uint32_t test_id)
> {
> struct kvm_run *run;
> @@ -181,6 +258,16 @@ static void vcpu_work(struct kvm_vm *vm, uint32_t test_id)
> continue;
> }
>
> + if (run->exit_reason == KVM_EXIT_HYPERCALL) {
> + handle_vm_exit_hypercall(run, test_id);
> + continue;
> + }
> +
> + if (run->exit_reason == KVM_EXIT_MEMORY_ERROR) {
> + handle_vm_exit_memory_error(run, test_id);
> + continue;
> + }
> +
> TEST_FAIL("Unhandled VCPU exit reason %d\n", run->exit_reason);
> break;
> }
>
Looks like you can easily combine lines without running into # chars limit
for several lines of code in this patch. If you haven't already, run
checkpatch to make sure coding guidelines are honored.
thanks,
-- Shuah
next prev parent reply other threads:[~2022-05-12 17:41 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 0:08 [RFC V2 PATCH 0/8] selftests: KVM: selftests for fd-based approach of supporting private memory Vishal Annapurve
2022-05-11 0:08 ` [RFC V2 PATCH 1/8] selftests: kvm: Fix inline assembly for hypercall Vishal Annapurve
2022-05-12 17:31 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 2/8] selftests: kvm: Add a basic selftest to test private memory Vishal Annapurve
2022-05-12 17:29 ` Shuah Khan
2022-07-20 23:03 ` Sean Christopherson
2022-07-21 20:24 ` Vishal Annapurve
2022-07-21 21:16 ` Sean Christopherson
2022-05-11 0:08 ` [RFC V2 PATCH 3/8] selftests: kvm: priv_memfd_test: Add support for memory conversion Vishal Annapurve
2022-05-12 17:40 ` Shuah Khan [this message]
2022-05-11 0:08 ` [RFC V2 PATCH 4/8] selftests: kvm: priv_memfd_test: Add shared access test Vishal Annapurve
2022-05-12 17:45 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 5/8] selftests: kvm: Add implicit memory conversion tests Vishal Annapurve
2022-05-12 17:48 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 6/8] selftests: kvm: Add KVM_HC_MAP_GPA_RANGE hypercall test Vishal Annapurve
2022-05-12 17:50 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 7/8] selftests: kvm: Add hugepage support to priv_memfd_test suite Vishal Annapurve
2022-05-12 17:51 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 8/8] selftests: kvm: priv_memfd: Add test avoiding double allocation Vishal Annapurve
2022-05-12 17:52 ` Shuah Khan
2022-05-11 0:08 ` [RFC V2 PATCH 8/8] selftests: kvm: priv_memfd: Add test without " Vishal Annapurve
2022-05-12 18:04 ` [RFC V2 PATCH 0/8] selftests: KVM: selftests for fd-based approach of supporting private memory Shuah Khan
2022-05-12 18:18 ` Vishal Annapurve
2022-07-20 22:19 ` Sean Christopherson
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=934a07be-ce72-7916-5614-e78af8293b5c@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=aaronlewis@google.com \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bfields@fieldses.org \
--cc=bp@alien8.de \
--cc=chao.p.peng@linux.intel.com \
--cc=corbet@lwn.net \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=diviness@google.com \
--cc=drjones@redhat.com \
--cc=erdemaktas@google.com \
--cc=hpa@zytor.com \
--cc=hughd@google.com \
--cc=jlayton@kernel.org \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=jun.nakajima@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@kernel.org \
--cc=marcorr@google.com \
--cc=michael.roth@amd.com \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=pbonzini@redhat.com \
--cc=pgonda@google.com \
--cc=qperret@google.com \
--cc=ricarkol@google.com \
--cc=seanjc@google.com \
--cc=shauh@kernel.org \
--cc=steven.price@arm.com \
--cc=tglx@linutronix.de \
--cc=vannapurve@google.com \
--cc=vbabka@suse.cz \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.w.wang@intel.com \
--cc=x86@kernel.org \
--cc=yang.zhong@intel.com \
--cc=yu.c.zhang@linux.intel.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