qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Jidong Xiao <jidong.xiao@gmail.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 21:36:41 +1000	[thread overview]
Message-ID: <1404128201.28960.32.camel@localhost> (raw)
In-Reply-To: <CAG4AFWYvVHLv0zuaPFsFPOAdExu57YLwT51ZqOUh0oCg=u=Vwg@mail.gmail.com>

On Mon, 2014-06-30 at 06:19 -0400, Jidong Xiao wrote:
> 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

Yes, but you don't have to support all the Hyper-V features at once. 
Hypervisor declares supported feature by specifying appropriate flags
in Feature identification (0x40000003) and Implementation
recommendations (0x40000004)CPUID leaves.

Best regards,
Vadim.

> --
> To unsubscribe from this list: send the line "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2014-06-30 11:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  1:39 [Qemu-devel] [questions] about KVM as a Microsoft-compatible hypervisor Zhang Haoyu
2014-06-30 10:02 ` Vadim Rozenfeld
2014-06-30 10:19   ` Jidong Xiao
2014-06-30 11:36     ` Vadim Rozenfeld [this message]
2014-06-30 11:45   ` [Qemu-devel] [questions] about KVM as a Microsoft-compatiblehypervisor Zhang Haoyu
2014-06-30 12:18     ` Vadim Rozenfeld
2014-08-04  2:17       ` [Qemu-devel] [questions] about KVM as aMicrosoft-compatiblehypervisor Zhang Haoyu
2014-08-04  5:09         ` Vadim Rozenfeld
2014-08-04  6:29         ` [Qemu-devel] [questions] about KVM asaMicrosoft-compatiblehypervisor Zhang Haoyu
2014-08-06  9:55           ` Vadim Rozenfeld

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=1404128201.28960.32.camel@localhost \
    --to=vrozenfe@redhat.com \
    --cc=jidong.xiao@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    --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).