public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Binbin Wu <binbin.wu@linux.intel.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: pbonzini@redhat.com, seanjc@google.com, isaku.yamahata@intel.com,
	rick.p.edgecombe@intel.com, michael.roth@amd.com,
	binbin.wu@linux.intel.com
Subject: [PATCH v2 0/2] KVM: x86: Check hypercall's exit to userspace generically
Date: Tue, 13 Aug 2024 13:12:54 +0800	[thread overview]
Message-ID: <20240813051256.2246612-1-binbin.wu@linux.intel.com> (raw)

Currently in kvm_emulate_hypercall, KVM_HC_MAP_GPA_RANGE is checked
specifically to decide whether a KVM hypercall needs to exit to userspace
or not.  Do the check based on the hypercall_exit_enabled field of
struct kvm_arch.

Also use the API is_kvm_hc_exit_enabled() to replace the opencode.

---
v2:
- Check the return value of __kvm_emulate_hypercall() before checking
  hypercall_exit_enabled to avoid an invalid KVM hypercall nr.
  https://lore.kernel.org/kvm/184d90a8-14a0-494a-9112-365417245911@linux.intel.com/
- Add a warning if a hypercall nr out of the range of hypercall_exit_enabled
  can express.

Binbin Wu (2):
  KVM: x86: Check hypercall's exit to userspace generically
  KVM: x86: Use is_kvm_hc_exit_enabled() instead of opencode

 arch/x86/kvm/svm/sev.c | 4 ++--
 arch/x86/kvm/x86.c     | 6 +++---
 arch/x86/kvm/x86.h     | 7 +++++++
 3 files changed, 12 insertions(+), 5 deletions(-)


base-commit: 332d2c1d713e232e163386c35a3ba0c1b90df83f
-- 
2.43.2


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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-13  5:12 Binbin Wu [this message]
2024-08-13  5:12 ` [PATCH v2 1/2] KVM: x86: Check hypercall's exit to userspace generically Binbin Wu
2024-08-13  5:56   ` Yuan Yao
2024-08-13  6:14     ` Yuan Yao
2024-08-13 17:50   ` Isaku Yamahata
2024-08-13 23:11     ` Huang, Kai
2024-08-14  0:52       ` Isaku Yamahata
2024-08-14  1:27         ` Binbin Wu
2024-08-14  1:31         ` Sean Christopherson
2024-08-14  2:36           ` Huang, Kai
2024-08-14  4:59           ` Binbin Wu
2024-08-13 23:16   ` Huang, Kai
2024-08-14  0:53     ` Isaku Yamahata
2024-08-14  1:08     ` Binbin Wu
2024-08-13  5:12 ` [PATCH v2 2/2] KVM: x86: Use is_kvm_hc_exit_enabled() instead of opencode Binbin Wu
2024-08-13 17:51   ` Isaku Yamahata
2024-08-13 23:18   ` Huang, Kai
2024-08-19 10:07     ` Binbin Wu
2024-08-19 22:24       ` Huang, Kai

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=20240813051256.2246612-1-binbin.wu@linux.intel.com \
    --to=binbin.wu@linux.intel.com \
    --cc=isaku.yamahata@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=rick.p.edgecombe@intel.com \
    --cc=seanjc@google.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