qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Vadim Rozenfeld <vrozenfe@redhat.com>
To: Zhang Haoyu <zhanghy@sangfor.com>
Cc: Jidong Xiao <jidong.xiao@gmail.com>,
	qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [questions] about KVM asaMicrosoft-compatiblehypervisor
Date: Wed, 06 Aug 2014 19:55:57 +1000	[thread overview]
Message-ID: <1407318957.11187.2.camel@oscar> (raw)
In-Reply-To: <201408041429531176607@sangfor.com>

On Mon, 2014-08-04 at 14:29 +0800, Zhang Haoyu wrote:
> >Hi Zhang,
> >
> >No I haven't seen such problem
> >Which kernel version are you running?
> Host kernel: RHEL7-RC1(linux-3.10.0).
> 
> >Does it include the latest lazy eli changes?
> >
> lazy eli or lazy eoi?
EOI
> How to confirm whether lazy eli has been included?
> 
not in linux-3.10.0
> >Btw, hv_spinlocks=0xfffffff is a pretty huge value.
> >
> which value do you advise to use?
MS seems to be using 0xffff as a default.
best regards,
Vadim.
> 
> Thanks,
> Zhang Haoyu
> >Best regards,
> >Vadim.
> 
> 

      reply	other threads:[~2014-08-06  9:56 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
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 [this message]

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=1407318957.11187.2.camel@oscar \
    --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).