From: "Denis V. Lunev" <den@openvz.org> Cc: Gleb Natapov <gleb@kernel.org>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, rkagan@virtuozzo.com, Paolo Bonzini <pbonzini@redhat.com>, Andrey Smetanin <asmetanin@virtuozzo.com>, "Denis V. Lunev" <den@openvz.org>, Vitaly Kuznetsov <vkuznets@redhat.com>, "K. Y. Srinivasan" <kys@microsoft.com> Subject: [Qemu-devel] [PATCH 0/2] Hyper-V synthetic interrupt controller Date: Fri, 9 Oct 2015 16:39:46 +0300 [thread overview] Message-ID: <1444397988-20167-1-git-send-email-den@openvz.org> (raw) This patchset implements the KVM part of the synthetic interrupt controller (synic) which is a building block of the Hyper-V paravirtualized device bus (vmbus). Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event flag page in the guest memory with 16 2048-bit per-SINT event flag areas The host triggers a SINT whenever it delivers a new message to the corresponding slot or flips an event flag bit in the corresponding area. The guest informs the host that it can try delivering a message by explicitly asserting EOI in lapic or writing to End-Of-Message (EOM) MSR. The userspace (qemu) triggers interrupts and receives EOM notifications via irqfd with resampler; for that, a GSI is allocated for each configured SINT, and irq_routing api is extended to support GSI-SINT mapping. Besides, a new vcpu exit is introduced to notify the userspace of the changes in synic configuraion triggered by guest writing to the corresponding MSRs. Signed-off-by: Andrey Smetanin <asmetanin@virtuozzo.com> Reviewed-by: Roman Kagan <rkagan@virtuozzo.com> Signed-off-by: Denis V. Lunev <den@openvz.org> CC: Vitaly Kuznetsov <vkuznets@redhat.com> CC: "K. Y. Srinivasan" <kys@microsoft.com> CC: Gleb Natapov <gleb@kernel.org> CC: Paolo Bonzini <pbonzini@redhat.com>
WARNING: multiple messages have this Message-ID (diff)
From: "Denis V. Lunev" <den@openvz.org> Cc: Gleb Natapov <gleb@kernel.org>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, rkagan@virtuozzo.com, Paolo Bonzini <pbonzini@redhat.com>, Andrey Smetanin <asmetanin@virtuozzo.com>, "Denis V. Lunev" <den@openvz.org>, Vitaly Kuznetsov <vkuznets@redhat.com> Subject: [PATCH 0/2] Hyper-V synthetic interrupt controller Date: Fri, 9 Oct 2015 16:39:46 +0300 [thread overview] Message-ID: <1444397988-20167-1-git-send-email-den@openvz.org> (raw) This patchset implements the KVM part of the synthetic interrupt controller (synic) which is a building block of the Hyper-V paravirtualized device bus (vmbus). Synic is a lapic extension, which is controlled via MSRs and maintains for each vCPU - 16 synthetic interrupt "lines" (SINT's); each can be configured to trigger a specific interrupt vector optionally with auto-EOI semantics - a message page in the guest memory with 16 256-byte per-SINT message slots - an event flag page in the guest memory with 16 2048-bit per-SINT event flag areas The host triggers a SINT whenever it delivers a new message to the corresponding slot or flips an event flag bit in the corresponding area. The guest informs the host that it can try delivering a message by explicitly asserting EOI in lapic or writing to End-Of-Message (EOM) MSR. The userspace (qemu) triggers interrupts and receives EOM notifications via irqfd with resampler; for that, a GSI is allocated for each configured SINT, and irq_routing api is extended to support GSI-SINT mapping. Besides, a new vcpu exit is introduced to notify the userspace of the changes in synic configuraion triggered by guest writing to the corresponding MSRs. Signed-off-by: Andrey Smetanin <asmetanin@virtuozzo.com> Reviewed-by: Roman Kagan <rkagan@virtuozzo.com> Signed-off-by: Denis V. Lunev <den@openvz.org> CC: Vitaly Kuznetsov <vkuznets@redhat.com> CC: "K. Y. Srinivasan" <kys@microsoft.com> CC: Gleb Natapov <gleb@kernel.org> CC: Paolo Bonzini <pbonzini@redhat.com>
next reply other threads:[~2015-10-09 13:40 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-09 13:39 Denis V. Lunev [this message] 2015-10-09 13:39 ` [PATCH 0/2] Hyper-V synthetic interrupt controller Denis V. Lunev 2015-10-09 13:39 ` [Qemu-devel] [PATCH 1/2] kvm/x86: " Denis V. Lunev 2015-10-09 13:39 ` Denis V. Lunev 2015-10-09 14:42 ` [Qemu-devel] " Paolo Bonzini 2015-10-09 14:42 ` Paolo Bonzini 2015-10-09 15:53 ` [Qemu-devel] " Roman Kagan 2015-10-09 15:58 ` Paolo Bonzini 2015-10-09 15:58 ` Paolo Bonzini 2015-10-09 15:53 ` Roman Kagan 2015-10-12 7:54 ` [Qemu-devel] " Christian Borntraeger 2015-10-12 7:54 ` Christian Borntraeger 2015-10-12 8:48 ` [Qemu-devel] " Cornelia Huck 2015-10-12 8:48 ` Cornelia Huck 2015-10-12 8:58 ` [Qemu-devel] " Paolo Bonzini 2015-10-12 8:58 ` Paolo Bonzini 2015-10-12 11:05 ` Roman Kagan 2015-10-12 11:05 ` [Qemu-devel] " Roman Kagan 2015-10-09 13:39 ` [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit Denis V. Lunev 2015-10-09 13:39 ` Denis V. Lunev 2015-10-09 14:41 ` [Qemu-devel] " Paolo Bonzini 2015-10-09 14:41 ` Paolo Bonzini 2015-10-09 14:53 ` [Qemu-devel] " Roman Kagan 2015-10-09 14:57 ` Paolo Bonzini 2015-10-09 14:57 ` Paolo Bonzini 2015-10-09 14:53 ` Roman Kagan 2015-10-12 13:42 ` [Qemu-devel] " Eric Blake 2015-10-12 13:42 ` Eric Blake 2015-10-12 13:44 ` Eric Blake 2015-10-12 13:44 ` Eric Blake 2015-10-12 13:46 ` Paolo Bonzini 2015-10-12 13:46 ` Paolo Bonzini 2015-10-12 13:46 ` Denis V. Lunev 2015-10-12 13:46 ` Denis V. Lunev 2015-10-12 22:21 ` KY Srinivasan 2015-10-12 22:21 ` KY Srinivasan 2015-10-12 13:52 ` Roman Kagan 2015-10-12 13: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=1444397988-20167-1-git-send-email-den@openvz.org \ --to=den@openvz.org \ --cc=asmetanin@virtuozzo.com \ --cc=gleb@kernel.org \ --cc=kys@microsoft.com \ --cc=pbonzini@redhat.com \ --cc=qemu-devel@nongnu.org \ --cc=rkagan@virtuozzo.com \ --cc=virtualization@lists.linux-foundation.org \ --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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.