From: Jidong Xiao <jidong.xiao@gmail.com>
To: Vadim Rozenfeld <vrozenfe@redhat.com>
Cc: Zhang Haoyu <zhanghy@sangfor.com>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [questions] about KVM as a Microsoft-compatible hypervisor
Date: Mon, 30 Jun 2014 06:19:51 -0400 [thread overview]
Message-ID: <CAG4AFWYvVHLv0zuaPFsFPOAdExu57YLwT51ZqOUh0oCg=u=Vwg@mail.gmail.com> (raw)
In-Reply-To: <1404122529.28960.24.camel@localhost>
On Mon, Jun 30, 2014 at 6:02 AM, Vadim Rozenfeld <vrozenfe@redhat.com> wrote:
> On Mon, 2014-06-30 at 09:39 +0800, Zhang Haoyu wrote:
>> Hi, Vadim
>> I read the kvm-2012-forum paper < KVM as a Microsoft-compatible hypervisor>,
>> Any update and other references, please?
>>
>> Thanks,
>> Zhang Haoyu
>>
>>
>
> Unfortunately, not too much.
> From the the most recent, we have lazy eoi implemented by
> MST and reference time counter.
>
> Best regards,
> Vadim.
>
It looks like that Mircosoft has defined a large number of synthetic
registers in their Hyper-v spec, so ultimately KVM should virtualize
most of these registers, so as to support the Mircosoft Enlightment,
right?
-Jidong
next prev parent reply other threads:[~2014-06-30 10:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 1:39 [questions] about KVM as a Microsoft-compatible hypervisor Zhang Haoyu
2014-06-30 10:02 ` [Qemu-devel] " Vadim Rozenfeld
2014-06-30 10:19 ` Jidong Xiao [this message]
2014-06-30 11:36 ` Vadim Rozenfeld
2014-06-30 11:45 ` Re: [Qemu-devel] [questions] about KVM as a Microsoft-compatiblehypervisor Zhang Haoyu
2014-06-30 12:18 ` Vadim Rozenfeld
2014-08-04 2:17 ` [questions] about KVM as aMicrosoft-compatiblehypervisor Zhang Haoyu
2014-08-04 5:09 ` [Qemu-devel] " Vadim Rozenfeld
2014-08-04 6:29 ` [Qemu-devel] [questions] about KVM asaMicrosoft-compatiblehypervisor Zhang Haoyu
2014-08-06 9:55 ` Vadim Rozenfeld
2014-08-08 3:51 ` [Qemu-devel] [questions] about KVMasaMicrosoft-compatiblehypervisor Zhang Haoyu
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='CAG4AFWYvVHLv0zuaPFsFPOAdExu57YLwT51ZqOUh0oCg=u=Vwg@mail.gmail.com' \
--to=jidong.xiao@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@redhat.com \
--cc=zhanghy@sangfor.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).