From: Sean Christopherson <seanjc@google.com>
To: Krish Sadhukhan <krish.sadhukhan@oracle.com>
Cc: kvm@vger.kernel.org, pbonzini@redhat.com, jmattson@google.com,
vkuznets@redhat.com, wanpengli@tencent.com, joro@8bytes.org
Subject: Re: [PATCH 1/2] nSVM: Add a variant of svm_vmrun() for executing custom guest code
Date: Thu, 15 Jul 2021 19:05:45 +0000 [thread overview]
Message-ID: <YPCHCX7rBvKXI0Ts@google.com> (raw)
In-Reply-To: <20210715180824.234781-2-krish.sadhukhan@oracle.com>
On Thu, Jul 15, 2021, Krish Sadhukhan wrote:
> Current implementation of svm_vmrun() and test_run() sets the guest RIP to a
> wrapper function which executes the guest code being used by tests. This is
> not suitable for tests like testing the effect of guest EFLAGS.TF on VMRUN
> because the trap handler will point to the second guest instruction to which
> the test code does not have access.
>
> Therefore, add a variant of svm_vmrun() that will set the guest RIP to the
> actual guest code that tests want to test. This will be used by the next
> patch in this series.
>
> Signed-off-by: Krish Sadhukhan <krish.sadhukhan@oracle.com>
> ---
> x86/svm.c | 14 ++++++++++++--
> x86/svm.h | 1 +
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/x86/svm.c b/x86/svm.c
> index f185ca0..50b6a15 100644
> --- a/x86/svm.c
> +++ b/x86/svm.c
> @@ -227,9 +227,9 @@ struct svm_test *v2_test;
>
> u64 guest_stack[10000];
>
> -int svm_vmrun(void)
> +static int _svm_vmrun(u64 rip)
I'd prefer to stay with the kernel style of two underscores for inner helpers.
> {
> - vmcb->save.rip = (ulong)test_thunk;
> + vmcb->save.rip = (ulong)rip;
> vmcb->save.rsp = (ulong)(guest_stack + ARRAY_SIZE(guest_stack));
> regs.rdi = (ulong)v2_test;
>
> @@ -244,6 +244,16 @@ int svm_vmrun(void)
> return (vmcb->control.exit_code);
> }
>
> +int svm_vmrun(void)
> +{
> + return _svm_vmrun((u64)test_thunk);
> +}
> +
> +int svm_vmrun_custom(u64 rip)
> +{
> + return _svm_vmrun(rip);
> +}
Why bother with the "custom" wrapper? Just expose the inner helper.
next prev parent reply other threads:[~2021-07-15 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-15 18:08 [PATCH 0/2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN Krish Sadhukhan
2021-07-15 18:08 ` [PATCH 1/2] nSVM: Add a variant of svm_vmrun() for executing custom guest code Krish Sadhukhan
2021-07-15 19:05 ` Sean Christopherson [this message]
2021-07-15 18:08 ` [PATCH 2/2] Test: nSVM: Test the effect of guest EFLAGS.TF on VMRUN Krish Sadhukhan
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=YPCHCX7rBvKXI0Ts@google.com \
--to=seanjc@google.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=krish.sadhukhan@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.