qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
	Andrey Smetanin <asmetanin@virtuozzo.com>,
	kvm@vger.kernel.org
Cc: Gleb Natapov <gleb@kernel.org>,
	Roman Kagan <rkagan@virtiozzo.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>,
	"K. Y. Srinivasan" <kys@microsoft.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 9/9] kvm/x86: Hyper-V kvm exit
Date: Mon, 26 Oct 2015 13:13:59 +0300	[thread overview]
Message-ID: <562DFCE7.40203@openvz.org> (raw)
In-Reply-To: <56290FF9.5080009@redhat.com>

On 10/22/2015 07:34 PM, Paolo Bonzini wrote:
>
> On 22/10/2015 18:10, Andrey Smetanin wrote:
>> A new vcpu exit is introduced to notify the userspace of the
>> changes in Hyper-V SynIC configuration triggered by guest writing to the
>> corresponding MSRs.
>>
>> Changes v3:
>> * added KVM_EXIT_HYPERV types and structs notes into docs
> Thanks.  The changes look good.  I look forward to the unit tests so I
> can merge it.
>
> Paolo

sent.

Den

  reply	other threads:[~2015-10-26 10:14 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-16  7:07 [Qemu-devel] [PATCH v2 0/9] Hyper-V synthetic interrupt controller Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 1/9] kvm/eventfd: avoid loop inside irqfd_update() Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 2/9] kvm/eventfd: factor out kvm_notify_acked_gsi() Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 3/9] kvm/eventfd: add arch-specific set_irq Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 4/9] kvm/irqchip: allow only multiple irqchip routes per GSI Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 5/9] kvm/irqchip: kvm_arch_irq_routing_update renaming split Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 6/9] drivers/hv: share Hyper-V SynIC constants with userspace Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 7/9] kvm/x86: split ioapic-handled and EOI exit bitmaps Denis V. Lunev
2015-10-16  7:07 ` [Qemu-devel] [PATCH 8/9] kvm/x86: Hyper-V synthetic interrupt controller Denis V. Lunev
2015-10-22 16:09   ` [Qemu-devel] [PATCH v3 " Andrey Smetanin
2015-10-28 17:41     ` Paolo Bonzini
2015-10-29  8:45       ` Roman Kagan
2015-10-29  9:51         ` Paolo Bonzini
2015-10-29  8:50       ` Andrey Smetanin
2015-10-16  7:07 ` [Qemu-devel] [PATCH 9/9] kvm/x86: Hyper-V kvm exit Denis V. Lunev
2015-10-16  7:51   ` Paolo Bonzini
2015-10-16 10:51     ` Roman Kagan
2015-10-22 16:10   ` [Qemu-devel] [PATCH v3 " Andrey Smetanin
2015-10-22 16:34     ` Paolo Bonzini
2015-10-26 10:13       ` Denis V. Lunev [this message]
2015-11-03 13:28     ` Paolo Bonzini
2015-11-03 13:30       ` Andrey Smetanin
2015-11-03 14:36       ` Andrey Smetanin
2015-11-03 14:51         ` Paolo Bonzini
2015-11-03 15:42           ` Andrey Smetanin
2015-11-03 15:52           ` 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=562DFCE7.40203@openvz.org \
    --to=den@openvz.org \
    --cc=asmetanin@virtuozzo.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=kys@microsoft.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rkagan@virtiozzo.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;
as well as URLs for NNTP newsgroup(s).