From: Roman Kagan <rkagan@virtuozzo.com>
To: kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>
Cc: "Denis V. Lunev" <den@openvz.org>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
David Hildenbrand <david@redhat.com>
Subject: [PATCH v3 0/2] kvm: x86: hyperv: guest->host event signaling via eventfd
Date: Thu, 7 Dec 2017 20:42:16 +0300 [thread overview]
Message-ID: <20171207174218.7962-1-rkagan@virtuozzo.com> (raw)
Make it possible for guests using Hyper-V emulation to do guest->host
notification via EVENT_SIGNAL hypercall without a user exit.
v2 -> v3:
- expand docs on allowed values and return codes
- fix uninitialized return
- style fixes
v1 -> v2:
- make data types consistent
- get by without the recently dropped struct hv_input_signal_event
- fix subject prefixes
Roman Kagan (2):
kvm: x86: factor out kvm.arch.hyperv (de)init
kvm: x86: hyperv: guest->host event signaling via eventfd
Documentation/virtual/kvm/api.txt | 31 ++++++++++
arch/x86/include/asm/kvm_host.h | 2 +
arch/x86/kvm/hyperv.h | 4 ++
include/uapi/linux/kvm.h | 13 ++++
arch/x86/kvm/hyperv.c | 123 +++++++++++++++++++++++++++++++++++++-
arch/x86/kvm/x86.c | 13 +++-
6 files changed, 184 insertions(+), 2 deletions(-)
--
2.14.3
next reply other threads:[~2017-12-07 17:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 17:42 Roman Kagan [this message]
2017-12-07 17:42 ` [PATCH v3 1/2] kvm: x86: factor out kvm.arch.hyperv (de)init Roman Kagan
2017-12-07 17:42 ` [PATCH v3 2/2] kvm: x86: hyperv: guest->host event signaling via eventfd Roman Kagan
2017-12-11 21:14 ` David Hildenbrand
2017-12-12 9:02 ` Roman Kagan
2017-12-12 9:37 ` David Hildenbrand
2017-12-12 10:17 ` Roman Kagan
2017-12-12 11:29 ` Roman Kagan
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=20171207174218.7962-1-rkagan@virtuozzo.com \
--to=rkagan@virtuozzo.com \
--cc=david@redhat.com \
--cc=den@openvz.org \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=rkrcmar@redhat.com \
--cc=vkuznets@redhat.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