From: Paolo Bonzini <pbonzini@redhat.com>
To: Peter Hornyack <peterhornyack@google.com>
Cc: kvm list <kvm@vger.kernel.org>, Gleb Natapov <gleb@kernel.org>,
Pavel Fedin <p.fedin@samsung.com>,
qemu-devel@nongnu.org, Roman Kagan <rkagan@virtuozzo.com>,
Andrey Smetanin <asmetanin@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>
Subject: Re: [Qemu-devel] [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit
Date: Fri, 18 Dec 2015 19:23:19 +0100 [thread overview]
Message-ID: <56744F17.20707@redhat.com> (raw)
In-Reply-To: <CA+0KQ4O82fH2wfrPM=dR68Hh=YpsbRnq5ErHACgxm+Q-yN8+2Q@mail.gmail.com>
On 18/12/2015 19:10, Peter Hornyack wrote:
> On brief inspection of Andrey's patch (I have not been following
> closely) it looks like the kvm_hyperv_exit struct that's returned to
> userspace contains more data (control, evt_page, and msg_page fields)
> than simply the value of the MSR, so would the desired SynIC exit fit
> into a general-purpose exit for MSR emulation?
This would be a special case that is used even if the hyperv MSRs are
emulated in the kernel. Other exit subcodes than
KVM_EXIT_(MSR_)HYPERV_SYNIC would be used for your usecase of for MSR
emulation in userspace.
Paolo
next prev parent reply other threads:[~2015-12-18 18:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-10 12:36 [Qemu-devel] [PATCH v4 0/5] KVM: Hyper-V synthetic interrupt controller Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] [PATCH v4 1/5] kvm/irqchip: kvm_arch_irq_routing_update renaming split Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] [PATCH v4 2/5] kvm/x86: split ioapic-handled and EOI exit bitmaps Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] [PATCH v4 3/5] kvm/x86: per-vcpu apicv deactivation support Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] [PATCH v4 4/5] kvm/x86: Hyper-V synthetic interrupt controller Andrey Smetanin
2015-11-10 12:36 ` [Qemu-devel] [PATCH v4 5/5] kvm/x86: Hyper-V kvm exit Andrey Smetanin
2015-12-18 15:19 ` Pavel Fedin
2015-12-18 15:53 ` Denis V. Lunev
2015-12-18 16:01 ` Paolo Bonzini
2015-12-18 18:10 ` Peter Hornyack
2015-12-18 18:23 ` Paolo Bonzini [this message]
2015-12-18 18:39 ` Roman Kagan
2015-12-21 12:59 ` Andrey Smetanin
2015-12-21 13:28 ` Pavel Fedin
2015-12-21 13:48 ` Andrey Smetanin
2015-12-21 15:21 ` Pavel Fedin
2015-12-18 18:25 ` 'Roman Kagan'
2015-12-21 7:44 ` Pavel Fedin
2015-12-18 18:00 ` '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=56744F17.20707@redhat.com \
--to=pbonzini@redhat.com \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=gleb@kernel.org \
--cc=kvm@vger.kernel.org \
--cc=p.fedin@samsung.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 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).