From: Pavel Fedin <p.fedin@samsung.com>
To: asmetanin@virtuozzo.com, 'Roman Kagan' <rkagan@virtuozzo.com>,
'Peter Hornyack' <peterhornyack@google.com>,
'Paolo Bonzini' <pbonzini@redhat.com>,
'kvm list' <kvm@vger.kernel.org>,
"'Denis V. Lunev'" <den@openvz.org>,
'Gleb Natapov' <gleb@kernel.org>,
qemu-devel@nongnu.org
Subject: RE: [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit
Date: Mon, 21 Dec 2015 16:28:12 +0300 [thread overview]
Message-ID: <003201d13bf3$714edae0$53ec90a0$@samsung.com> (raw)
In-Reply-To: <5677F7C5.5040404@virtuozzo.com>
Hello!
> Yes, we can use KVM_EXIT_REG_IO/MSR_IO for Hyper-V SynIC MSRS's changes
> and can even use only one MSR value . So union inside struct
> kvm_hyperv_exit is excessive.
>
> But we still need Vcpu exit to handle VMBus hypercalls by QEMU to
> emulate VMBus devices inside QEMU.
>
> And currently we are going to extend struct kvm_hyperv_exit
> to store Hyper-V VMBus hypercall parameters.
Hm... Hypercalls, you say?
We already have KVM_EXIT_HYPERCALL. Documentation says it's currently unused. Is it a leftover from ia64 KVM? Could we reuse it for
the purpose?
> but could we replace Hyper-V VMBus hypercall and it's parameters
> by KVM_EXIT_REG_IO/MSR_IO too?
It depends. Can i read about these hypercalls somewhere? Is there any documentation?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Fedin <p.fedin@samsung.com>
To: asmetanin@virtuozzo.com, 'Roman Kagan' <rkagan@virtuozzo.com>,
'Peter Hornyack' <peterhornyack@google.com>,
'Paolo Bonzini' <pbonzini@redhat.com>,
'kvm list' <kvm@vger.kernel.org>,
"'Denis V. Lunev'" <den@openvz.org>,
'Gleb Natapov' <gleb@kernel.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit
Date: Mon, 21 Dec 2015 16:28:12 +0300 [thread overview]
Message-ID: <003201d13bf3$714edae0$53ec90a0$@samsung.com> (raw)
In-Reply-To: <5677F7C5.5040404@virtuozzo.com>
Hello!
> Yes, we can use KVM_EXIT_REG_IO/MSR_IO for Hyper-V SynIC MSRS's changes
> and can even use only one MSR value . So union inside struct
> kvm_hyperv_exit is excessive.
>
> But we still need Vcpu exit to handle VMBus hypercalls by QEMU to
> emulate VMBus devices inside QEMU.
>
> And currently we are going to extend struct kvm_hyperv_exit
> to store Hyper-V VMBus hypercall parameters.
Hm... Hypercalls, you say?
We already have KVM_EXIT_HYPERCALL. Documentation says it's currently unused. Is it a leftover from ia64 KVM? Could we reuse it for
the purpose?
> but could we replace Hyper-V VMBus hypercall and it's parameters
> by KVM_EXIT_REG_IO/MSR_IO too?
It depends. Can i read about these hypercalls somewhere? Is there any documentation?
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-12-21 13:28 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:36 [PATCH v4 0/5] KVM: Hyper-V synthetic interrupt controller Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-11-10 12:36 ` [PATCH v4 1/5] kvm/irqchip: kvm_arch_irq_routing_update renaming split Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-11-10 12:36 ` [PATCH v4 2/5] kvm/x86: split ioapic-handled and EOI exit bitmaps Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-11-10 12:36 ` [PATCH v4 3/5] kvm/x86: per-vcpu apicv deactivation support Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-11-10 12:36 ` [PATCH v4 4/5] kvm/x86: Hyper-V synthetic interrupt controller Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-11-10 12:36 ` [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] " Andrey Smetanin
2015-12-18 15:19 ` Pavel Fedin
2015-12-18 15:19 ` [Qemu-devel] " Pavel Fedin
2015-12-18 15:53 ` Denis V. Lunev
2015-12-18 15:53 ` [Qemu-devel] " Denis V. Lunev
2015-12-18 16:01 ` Paolo Bonzini
2015-12-18 16:01 ` [Qemu-devel] " Paolo Bonzini
2015-12-18 18:10 ` Peter Hornyack
2015-12-18 18:10 ` [Qemu-devel] " Peter Hornyack
2015-12-18 18:23 ` Paolo Bonzini
2015-12-18 18:23 ` [Qemu-devel] " Paolo Bonzini
2015-12-18 18:39 ` Roman Kagan
2015-12-18 18:39 ` [Qemu-devel] " Roman Kagan
2015-12-21 12:59 ` Andrey Smetanin
2015-12-21 12:59 ` [Qemu-devel] " Andrey Smetanin
2015-12-21 13:28 ` Pavel Fedin [this message]
2015-12-21 13:28 ` Pavel Fedin
2015-12-21 13:48 ` Andrey Smetanin
2015-12-21 13:48 ` [Qemu-devel] " Andrey Smetanin
2015-12-21 15:21 ` Pavel Fedin
2015-12-21 15:21 ` [Qemu-devel] " Pavel Fedin
2015-12-18 18:25 ` 'Roman Kagan'
2015-12-18 18:25 ` [Qemu-devel] " 'Roman Kagan'
2015-12-21 7:44 ` Pavel Fedin
2015-12-21 7:44 ` [Qemu-devel] " Pavel Fedin
2015-12-18 18:00 ` 'Roman Kagan'
2015-12-18 18:00 ` [Qemu-devel] " '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='003201d13bf3$714edae0$53ec90a0$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterhornyack@google.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.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 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.