From: Forrest Yuan Yu <yuanyu@google.com>
To: kvm@vger.kernel.org
Cc: Forrest Yuan Yu <yuanyu@google.com>
Subject: [PATCH RFC 0/1] Hypercall UCALL for guest/userspace communication
Date: Fri, 1 May 2020 11:51:46 -0700 [thread overview]
Message-ID: <20200501185147.208192-1-yuanyu@google.com> (raw)
This RFC is to add a hypercall UCALL so that guest can communicate with
the userspace hypervisor. A guest may want to do this in different
scenarios. For example, a guest can ask the userspace hypervisor to
harden security by setting restricted access permissions on guest SLAT
entries.
Please note this hypercall provides the infrastructure for this type of
communication but does not enforce the protocol. A proposal for the
guest/userspace communication protocol will follow if this RFC is
accepted.
Forrest Yuan Yu (1):
KVM: x86: add KVM_HC_UCALL hypercall
Documentation/virt/kvm/api.rst | 15 +-
Documentation/virt/kvm/cpuid.rst | 3 +
Documentation/virt/kvm/hypercalls.rst | 14 ++
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/include/uapi/asm/kvm_para.h | 1 +
arch/x86/kvm/x86.c | 39 +++-
include/uapi/linux/kvm.h | 1 +
include/uapi/linux/kvm_para.h | 1 +
tools/testing/selftests/kvm/.gitignore | 1 +
tools/testing/selftests/kvm/Makefile | 1 +
.../selftests/kvm/x86_64/hypercall_ucall.c | 195 ++++++++++++++++++
11 files changed, 264 insertions(+), 8 deletions(-)
create mode 100644 tools/testing/selftests/kvm/x86_64/hypercall_ucall.c
--
2.26.2.526.g744177e7f7-goog
next reply other threads:[~2020-05-01 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 18:51 Forrest Yuan Yu [this message]
2020-05-01 18:51 ` [PATCH RFC 1/1] KVM: x86: add KVM_HC_UCALL hypercall Forrest Yuan Yu
2020-05-01 20:45 ` Sean Christopherson
2020-05-02 1:05 ` Liran Alon
2020-05-05 18:49 ` Jim Mattson
2020-05-05 23:53 ` Forrest Yuan Yu
2020-05-05 22:50 ` Forrest Yuan Yu
2020-05-01 20:23 ` [PATCH RFC 0/1] Hypercall UCALL for guest/userspace communication 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=20200501185147.208192-1-yuanyu@google.com \
--to=yuanyu@google.com \
--cc=kvm@vger.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