From: Eric Blake <eblake@redhat.com> To: "Denis V. Lunev" <den@openvz.org> Cc: Gleb Natapov <gleb@kernel.org>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, rkagan@virtuozzo.com, Andrey Smetanin <asmetanin@virtuozzo.com>, Paolo Bonzini <pbonzini@redhat.com>, Vitaly Kuznetsov <vkuznets@redhat.com>, "K. Y. Srinivasan" <kys@microsoft.com> Subject: Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit Date: Mon, 12 Oct 2015 07:44:28 -0600 [thread overview] Message-ID: <561BB93C.9050409@redhat.com> (raw) In-Reply-To: <561BB8D2.60402@redhat.com> [-- Attachment #1: Type: text/plain, Size: 921 bytes --] On 10/12/2015 07:42 AM, Eric Blake wrote: > On 10/09/2015 07:39 AM, Denis V. Lunev wrote: >> From: Andrey Smetanin <asmetanin@virtuozzo.com> >> >> A new vcpu exit is introduced to notify the userspace of the >> changes in Hyper-V synic configuraion triggered by guest writing to the > > s/configuraion/configuration/ > Is 'synic' intended? Is it short for something (if so, spelling it out > may help)? Ah, I see it now from patch 1/2: SYNthetic Interrupt Controller. >> +related with Hyper-V emulation. Currently used to synchronize modified >> +Hyper-V synic state with userspace. > > Again, is 'synic' intended? Hmm, I see it throughout the patch, so it > looks intentional, but I keep trying to read it as a typo for 'sync'. Don't know if SynIC would make it any easier to read? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org [-- Attachment #2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 604 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Eric Blake <eblake@redhat.com> To: "Denis V. Lunev" <den@openvz.org> Cc: Gleb Natapov <gleb@kernel.org>, qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, rkagan@virtuozzo.com, Andrey Smetanin <asmetanin@virtuozzo.com>, Paolo Bonzini <pbonzini@redhat.com>, Vitaly Kuznetsov <vkuznets@redhat.com> Subject: Re: [Qemu-devel] [PATCH 2/2] kvm/x86: Hyper-V kvm exit Date: Mon, 12 Oct 2015 07:44:28 -0600 [thread overview] Message-ID: <561BB93C.9050409@redhat.com> (raw) In-Reply-To: <561BB8D2.60402@redhat.com> [-- Attachment #1.1: Type: text/plain, Size: 921 bytes --] On 10/12/2015 07:42 AM, Eric Blake wrote: > On 10/09/2015 07:39 AM, Denis V. Lunev wrote: >> From: Andrey Smetanin <asmetanin@virtuozzo.com> >> >> A new vcpu exit is introduced to notify the userspace of the >> changes in Hyper-V synic configuraion triggered by guest writing to the > > s/configuraion/configuration/ > Is 'synic' intended? Is it short for something (if so, spelling it out > may help)? Ah, I see it now from patch 1/2: SYNthetic Interrupt Controller. >> +related with Hyper-V emulation. Currently used to synchronize modified >> +Hyper-V synic state with userspace. > > Again, is 'synic' intended? Hmm, I see it throughout the patch, so it > looks intentional, but I keep trying to read it as a typo for 'sync'. Don't know if SynIC would make it any easier to read? -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org [-- Attachment #1.2: OpenPGP digital signature --] [-- Type: application/pgp-signature, Size: 604 bytes --] [-- Attachment #2: Type: text/plain, Size: 183 bytes --] _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2015-10-12 13:44 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-10-09 13:39 [Qemu-devel] [PATCH 0/2] Hyper-V synthetic interrupt controller Denis V. Lunev 2015-10-09 13:39 ` 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 [this message] 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=561BB93C.9050409@redhat.com \ --to=eblake@redhat.com \ --cc=asmetanin@virtuozzo.com \ --cc=den@openvz.org \ --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.