All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Binbin Wu <binbin.wu@linux.intel.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	 Tom Lendacky <thomas.lendacky@amd.com>,
	Isaku Yamahata <isaku.yamahata@intel.com>,
	 Kai Huang <kai.huang@intel.com>,
	Xiaoyao Li <xiaoyao.li@intel.com>,
	 Adrian Hunter <adrian.hunter@intel.com>,
	Rick Edgecombe <rick.p.edgecombe@intel.com>
Subject: Re: [PATCH v4 0/6] KVM: x86: Prep KVM hypercall handling for TDX
Date: Fri, 17 Jan 2025 11:31:01 -0800	[thread overview]
Message-ID: <Z4qv9VTs0CZ0zoxW@google.com> (raw)
In-Reply-To: <67f0292e-6eea-4788-977c-50af51910945@linux.intel.com>

On Wed, Jan 15, 2025, Binbin Wu wrote:
> On 12/19/2024 10:40 AM, Sean Christopherson wrote:
> > On Wed, 27 Nov 2024 16:43:38 -0800, Sean Christopherson wrote:
> > > Effectively v4 of Binbin's series to handle hypercall exits to userspace in
> > > a generic manner, so that TDX
> > > 
> > > Binbin and Kai, this is fairly different that what we last discussed.  While
> > > sorting through Binbin's latest patch, I stumbled on what I think/hope is an
> > > approach that will make life easier for TDX.  Rather than have common code
> > > set the return value, _and_ have TDX implement a callback to do the same for
> > > user return MSRs, just use the callback for all paths.
> > > 
> > > [...]
> > Applied patch 1 to kvm-x86 fixes.  I'm going to hold off on the rest until the
> > dust settles on the SEAMCALL interfaces, e.g. in case TDX ends up marshalling
> > state into the "normal" GPRs.
> Hi Sean, Based on your suggestions in the link
> https://lore.kernel.org/kvm/Z1suNzg2Or743a7e@google.com, the v2 of "KVM: TDX:
> TDX hypercalls may exit to userspace" is planned to morph the TDG.VP.VMCALL
> with KVM hypercall to EXIT_REASON_VMCALL and marshall r10~r14 from
> vp_enter_args in struct vcpu_tdx to the appropriate x86 registers for KVM
> hypercall handling.

...

> To test TDX, I made some modifications to your patch
> "KVM: x86: Refactor __kvm_emulate_hypercall() into a macro"
> Are the following changes make sense to you?

Yes, but I think we can go a step further and effectively revert the bulk of commit
e913ef159fad ("KVM: x86: Split core of hypercall emulation to helper function"),
i.e. have ____kvm_emulate_hypercall() read the GPRs instead of passing them in
via the macro.

> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index a2198807290b..2c5df57ad799 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -10088,9 +10088,7 @@ int kvm_emulate_hypercall(struct kvm_vcpu *vcpu)
>         if (kvm_hv_hypercall_enabled(vcpu))
>                 return kvm_hv_hypercall(vcpu);
> -       return __kvm_emulate_hypercall(vcpu, rax, rbx, rcx, rdx, rsi,
> -                                      is_64_bit_hypercall(vcpu),
> -                                      kvm_x86_call(get_cpl)(vcpu),
> +       return __kvm_emulate_hypercall(vcpu, kvm_x86_call(get_cpl)(vcpu),
>                                        complete_hypercall_exit);
>  }
>  EXPORT_SYMBOL_GPL(kvm_emulate_hypercall);
> diff --git a/arch/x86/kvm/x86.h b/arch/x86/kvm/x86.h
> index b00ecbfef000..989bed5b48b0 100644
> --- a/arch/x86/kvm/x86.h
> +++ b/arch/x86/kvm/x86.h
> @@ -623,19 +623,18 @@ int ____kvm_emulate_hypercall(struct kvm_vcpu *vcpu, unsigned long nr,
>                               int op_64_bit, int cpl,
>                               int (*complete_hypercall)(struct kvm_vcpu *));
> -#define __kvm_emulate_hypercall(_vcpu, nr, a0, a1, a2, a3, op_64_bit, cpl, complete_hypercall) \
> -({                                                                                             \
> -       int __ret;                                                                              \
> -                                                                                               \
> -       __ret = ____kvm_emulate_hypercall(_vcpu,                                                \
> -                                         kvm_##nr##_read(_vcpu), kvm_##a0##_read(_vcpu),       \
> -                                         kvm_##a1##_read(_vcpu), kvm_##a2##_read(_vcpu),       \
> -                                         kvm_##a3##_read(_vcpu), op_64_bit, cpl,               \
> -                                         complete_hypercall);                                  \
> -                                                                                               \
> -       if (__ret > 0)                                                                          \
> -               __ret = complete_hypercall(_vcpu);                                              \
> -       __ret;                                                                                  \
> +#define __kvm_emulate_hypercall(_vcpu, cpl, complete_hypercall)                                \
> +({                                                                                     \
> +       int __ret;                                                                      \
> +       __ret = ____kvm_emulate_hypercall(_vcpu, kvm_rax_read(_vcpu),                   \
> +                                         kvm_rbx_read(_vcpu), kvm_rcx_read(_vcpu),     \
> +                                         kvm_rdx_read(_vcpu), kvm_rsi_read(_vcpu),     \
> +                                         is_64_bit_hypercall(_vcpu), cpl,              \
> +                                         complete_hypercall);                          \
> +                                                                                       \
> +       if (__ret > 0)                                                                  \
> +               __ret = complete_hypercall(_vcpu);                                      \
> +       __ret;                                                                          \
>  })
>  int kvm_emulate_hypercall(struct kvm_vcpu *vcpu);
> 
> 

  reply	other threads:[~2025-01-17 19:31 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-28  0:43 [PATCH v4 0/6] KVM: x86: Prep KVM hypercall handling for TDX Sean Christopherson
2024-11-28  0:43 ` [PATCH v4 1/6] KVM: x86: Play nice with protected guests in complete_hypercall_exit() Sean Christopherson
2024-11-28  3:22   ` Xiaoyao Li
2024-11-29  9:01   ` Nikunj A. Dadhania
2024-12-02 18:54   ` Tom Lendacky
2024-12-03  7:29   ` Binbin Wu
2024-11-28  0:43 ` [PATCH v4 2/6] KVM: x86: Add a helper to check for user interception of KVM hypercalls Sean Christopherson
2024-12-02 18:57   ` Tom Lendacky
2024-11-28  0:43 ` [PATCH v4 3/6] KVM: x86: Move "emulate hypercall" function declarations to x86.h Sean Christopherson
2024-11-28  3:23   ` Xiaoyao Li
2024-12-02 20:05   ` Tom Lendacky
2024-12-03  7:33   ` Binbin Wu
2024-11-28  0:43 ` [PATCH v4 4/6] KVM: x86: Bump hypercall stat prior to fully completing hypercall Sean Christopherson
2024-11-28  3:24   ` Xiaoyao Li
2024-12-02 20:13   ` Tom Lendacky
2024-12-02 20:33     ` Tom Lendacky
2024-12-03  7:37   ` Binbin Wu
2024-11-28  0:43 ` [PATCH v4 5/6] KVM: x86: Always complete hypercall via function callback Sean Christopherson
2024-11-28  3:08   ` Xiaoyao Li
2024-12-02 18:44     ` Sean Christopherson
2024-12-02 20:57   ` Tom Lendacky
2024-12-02 20:59     ` Tom Lendacky
2024-12-03  0:14       ` Sean Christopherson
2024-11-28  0:43 ` [PATCH v4 6/6] KVM: x86: Refactor __kvm_emulate_hypercall() into a macro Sean Christopherson
2024-11-28  8:38   ` Adrian Hunter
2024-12-10 16:20     ` Paolo Bonzini
2024-12-10 20:03       ` Sean Christopherson
2024-12-12  7:32         ` Adrian Hunter
2024-12-12 15:42           ` Paolo Bonzini
2024-12-12 18:40           ` Sean Christopherson
2024-12-03  8:01   ` Binbin Wu
2024-12-10 16:17   ` Paolo Bonzini
2024-12-10 20:10     ` Sean Christopherson
2024-11-28  1:06 ` [PATCH v4 0/6] KVM: x86: Prep KVM hypercall handling for TDX Huang, Kai
2024-12-19  2:40 ` Sean Christopherson
2025-01-15  9:40   ` Binbin Wu
2025-01-17 19:31     ` Sean Christopherson [this message]
2025-01-20  0:37       ` Binbin Wu
2025-01-21 18:04         ` 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=Z4qv9VTs0CZ0zoxW@google.com \
    --to=seanjc@google.com \
    --cc=adrian.hunter@intel.com \
    --cc=binbin.wu@linux.intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kai.huang@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=thomas.lendacky@amd.com \
    --cc=xiaoyao.li@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 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.