From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"Liu, RongrongX" <rongrongx.liu@intel.com>
Subject: Re: hyper-v support in KVM
Date: Wed, 12 Feb 2014 18:41:47 +1100 [thread overview]
Message-ID: <1392190907.22333.44.camel@w7-rhel> (raw)
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A9D9956@SHSMSX104.ccr.corp.intel.com>
On Wed, 2014-02-12 at 01:33 +0000, Zhang, Yang Z wrote:
> Vadim Rozenfeld wrote on 2014-02-10:
> > On Mon, 2014-02-10 at 08:21 +0000, Zhang, Yang Z wrote:
> >> Hi Vadim,
> >>
> >> Do you know the latest status of Hyper-v Enlightenments supporting in KVM?
> > Like how many Hyper-v interfaces are supported in KVM?
> >
> > Hi Yang,
> >
> > There is no many at the moment. KVM currently supports the following
> > Hyper-V features:
> >
> > Guest Spinlocks
> > http://msdn.microsoft.com/en-us/library/windows/hardware/ff539081%
> > 28v=vs.85%29.aspx
> >
> > Local APIC MSR Accesses
> > http://msdn.microsoft.com/en-us/library/windows/hardware/ff542396%
> > 28v=vs.85%29.aspx
> >
> > Reference Time Counter
> > http://msdn.microsoft.com/en-us/library/windows/hardware/ff542637%
> > 28v=vs.85%29.aspx
> >
> > We are going to add: Reference TSC Page
> > http://msdn.microsoft.com/en-us/library/windows/hardware/ff542643%
> > 28v=vs.85%29.aspx
> >
> > Lazy EOI support, maybe more.
> >
>
> Thanks for your update. More questions:
> I want to measure the performance improvement with hyper-v features enabled. So I want to know:
> Are those features enabled by default in KVM?
In KVM - yes, but you also need to specify them in QEMU command line.
They can be enabled by -cpu features hv_vapic, hv_spinlocks, hv_time,
and hv_relaxed
> How to turn off/on it manually?
Yes. From the QEMU command line.
> And how can I know whether guest is using it really?
There are two options - printk from the KVM side or
WinDbg from the guest side. But in case of hv_time
you can check the value returned by QueryPerformanceFrequency
http://msdn.microsoft.com/en-us/library/windows/desktop/ms644905%
28v=vs.85%29.aspx
it should be 10MHz
> Also, Do you have any performance data?
http://www.linux-kvm.org/wiki/images/0/0a/2012-forum-kvm_hyperv.pdf
pp 16, 18
I compared DPC and ISR times with xperf for two cases - with and without
enlightenment.
I also have seen reports mentioned around 5-10 percent CPU usage drop on
the host side, when loading guest with some disk-stress tests.
>
> > Kind regards.
> > Vadim.
> >
> >>
> >> best regards
> >> yang
> >>
> >> --
> >> 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
> >
> >
>
>
> Best regards,
> Yang
>
>
next prev parent reply other threads:[~2014-02-12 7:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-10 8:21 hyper-v support in KVM Zhang, Yang Z
2014-02-10 9:53 ` Vadim Rozenfeld
2014-02-12 1:33 ` Zhang, Yang Z
2014-02-12 7:41 ` Vadim Rozenfeld [this message]
2014-02-14 2:35 ` Liu, RongrongX
2014-02-14 5:36 ` Vadim Rozenfeld
2014-02-24 3:01 ` Zhang, Yang Z
2014-02-24 8:22 ` Vadim Rozenfeld
2014-02-24 8:35 ` Zhang, Yang Z
2014-02-24 9:33 ` 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=1392190907.22333.44.camel@w7-rhel \
--to=vrozenfe@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rongrongx.liu@intel.com \
--cc=yang.z.zhang@intel.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