public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: "Hao, Xudong" <xudong.hao@intel.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: KVM Test report, kernel e6a9246... qemu 94f964d...
Date: Tue, 07 Sep 2010 11:15:05 +0300	[thread overview]
Message-ID: <4C85F489.306@redhat.com> (raw)
In-Reply-To: <BC00F5384FCFC9499AF06F92E8B78A9E183AEA6E96@shsmsx502.ccr.corp.intel.com>

  On 09/07/2010 10:22 AM, Hao, Xudong wrote:
>
>> I never assigned a pci device in my life...
> Avi, I assumed your platform has no EPT hardware feature, right?

Correct.

> I tried sevral platforms, if I used no EPT suported machine, everything is OK as yours; if I used EPT supported machine, and then disable EPT with "modprobe kvm_intel ept=0", then issue happen.

That's what I thought - probably vpid+shadow interaction.  I'll test it out.

I usually test on an old machine since shadow is much more stressful 
than ept.  But shadow+vpid is even more stressful, I'll move my testing 
there.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2010-09-07  8:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-06  3:05 KVM Test report, kernel e6a9246... qemu 94f964d Hao, Xudong
2010-09-06  6:55 ` Avi Kivity
2010-09-06  6:59   ` Hao, Xudong
2010-09-06  8:04     ` Avi Kivity
2010-09-06  8:08       ` Hao, Xudong
2010-09-06  8:56         ` Avi Kivity
2010-09-07  0:51           ` Hao, Xudong
2010-09-07  7:22           ` Hao, Xudong
2010-09-07  8:15             ` Avi Kivity [this message]
2010-09-07  8:54               ` Sheng Yang
2010-09-07 11:27                 ` Avi Kivity
2010-09-07 12:04                   ` Avi Kivity
2010-09-07 12:31                     ` Avi Kivity
2010-09-07 13:23                       ` Avi Kivity
2010-09-08  0:35                         ` Sheng Yang

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=4C85F489.306@redhat.com \
    --to=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=xudong.hao@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