From: Paolo Bonzini <pbonzini@redhat.com>
To: Roman Kagan <rkagan@virtuozzo.com>, qemu-devel@nongnu.org
Cc: Vijayabhaskar Balakrishna <vijay.balakrishna@oracle.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Venu Busireddy <venu.busireddy@oracle.com>,
Liran Alon <liran.alon@oracle.com>,
Igor Mammedov <imammedo@redhat.com>,
Si-Wei Liu <si-wei.liu@oracle.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Karl Heubaum <karl.heubaum@oracle.com>
Subject: Re: [Qemu-devel] [PATCH 00/10] hyperv: add connection infrastructure
Date: Wed, 3 Oct 2018 13:12:10 +0200 [thread overview]
Message-ID: <54f9804b-405d-e587-73c5-0fc9b9aa07b7@redhat.com> (raw)
In-Reply-To: <20180921082217.29481-1-rkagan@virtuozzo.com>
On 21/09/2018 10:22, Roman Kagan wrote:
> This series introduces the infrastructure to send and receive Hyper-V
> messages and events.
>
> More specifically,
>
> - SynIC is turned into a full-fledged device managing the memory regions
> used for QEMU->guest communication
> - machinery is introduced to post messages and signal events to the
> guest
> - infrastructure is added to subscribe to messages and events from the
> guest, and to dispatch the received messages and events to the
> subscribers
>
> Based-on: 20180921082041.29380-1-rkagan@virtuozzo.com
>
> Roman Kagan (10):
> hyperv:synic: split capability testing and setting
> hyperv: qom-ify SynIC
> hyperv: only add SynIC in compatible configurations
> hyperv: make overlay pages for SynIC
> hyperv: add synic message delivery
> hyperv: add synic event flag signaling
> hyperv: process SIGNAL_EVENT hypercall
> hyperv: add support for KVM_HYPERV_EVENTFD
> hyperv: process POST_MESSAGE hypercall
> hyperv_testdev: add SynIC message and event testmodes
>
> include/hw/hyperv/hyperv-proto.h | 1 +
> include/hw/hyperv/hyperv.h | 58 +++-
> include/hw/i386/pc.h | 8 +
> target/i386/cpu.h | 1 +
> target/i386/hyperv.h | 4 +
> hw/hyperv/hyperv.c | 542 ++++++++++++++++++++++++++++++-
> hw/misc/hyperv_testdev.c | 165 +++++++++-
> target/i386/cpu.c | 2 +
> target/i386/hyperv-stub.c | 13 +
> target/i386/hyperv.c | 54 ++-
> target/i386/kvm.c | 45 ++-
> target/i386/machine.c | 9 +
> 12 files changed, 872 insertions(+), 30 deletions(-)
>
I queued all three series, though if I were to post a pull request now
I'd stop before "hyperv: add synic message delivery".
Paolo
next prev parent reply other threads:[~2018-10-03 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180921082217.29481-1-rkagan@virtuozzo.com>
[not found] ` <20180921082217.29481-6-rkagan@virtuozzo.com>
2018-10-03 11:06 ` [Qemu-devel] [PATCH 05/10] hyperv: add synic message delivery Paolo Bonzini
2018-10-03 13:01 ` Roman Kagan
2018-10-03 11:12 ` Paolo Bonzini [this message]
2018-10-03 14:25 ` [Qemu-devel] [PATCH 00/10] hyperv: add connection infrastructure Roman Kagan
2018-10-03 14:35 ` Paolo Bonzini
[not found] ` <20180921082217.29481-4-rkagan@virtuozzo.com>
2018-11-20 13:41 ` [Qemu-devel] [PATCH 03/10] hyperv: only add SynIC in compatible configurations Eduardo Habkost
2018-11-26 14:45 ` Igor Mammedov
2018-11-26 15:17 ` 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=54f9804b-405d-e587-73c5-0fc9b9aa07b7@redhat.com \
--to=pbonzini@redhat.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=karl.heubaum@oracle.com \
--cc=konrad.wilk@oracle.com \
--cc=liran.alon@oracle.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=si-wei.liu@oracle.com \
--cc=venu.busireddy@oracle.com \
--cc=vijay.balakrishna@oracle.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;
as well as URLs for NNTP newsgroup(s).