public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: lidong chen <chen.lidong.kernel@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, kvm@vger.kernel.org
Subject: Re: Why so many vm exits caused by ept violation
Date: Tue, 9 Nov 2010 11:27:27 +0200	[thread overview]
Message-ID: <20101109092727.GL9036@redhat.com> (raw)
In-Reply-To: <AANLkTinnYggVA3vCU=AOfQvtdcK=3qLrXEmp0Ugo6Psa@mail.gmail.com>

On Tue, Nov 09, 2010 at 05:04:15PM +0800, lidong chen wrote:
> how to configure virtio to use MSI? I didn't found out it.
> thanks.
> 
It looks like it should be enabled by default. What is you guest?

> 2010/11/9 Gleb Natapov <gleb@redhat.com>:
> > On Tue, Nov 09, 2010 at 03:37:44PM +0800, lidong chen wrote:
> >> sorry,i take mistake,
> >>
> >> the ept violation is not caused by 2M hugepages, but caused by e1000
> >> emulated by qemu.
> >> I test uesd 2M hugepages and virio, the performance is better than
> >> e1000. but is still worse than xen. I will continue to find out other
> >> reason.
> >>
> >>
> >>
> >> so, there are two question:
> >> 1.why have so many ept violation when used e1000?
> >>
> >>
> >> 2.when used virtio, there ara also such error happen.is this normal?
> >> I add the printk in function tdp_page_fault below.
> >>         pfn = gfn_to_pfn(vcpu->kvm, gfn);
> >>         if (is_error_pfn(pfn)) {
> >>                 kvm_release_pfn_clean(pfn);
> >>                 if( printk_ratelimit() ) {
> >>                         printk(KERN_EMERG "error gpa is %ld\n", gpa);
> >>                 }
> >>                 return is_fault_pfn(pfn) ? -EFAULT : 1;
> >>         }
> >>
> >> and result is:
> >> [root@rhel6-kvm1 ~]# dmesg -c
> >> __ratelimit: 387 callbacks suppressed
> >> error gpa is 4273995776
> >> error gpa is 4273995776
> >> error gpa is 4273995776
> >> error gpa is 4273995776
> >> error gpa is 4273995776
> >>
> > You should really print this in hex :) This is 0xfec00000 AKA
> > IOAPIC. Try to configure virtio to use MSI.
> >
> > --
> >                        Gleb.
> >

--
			Gleb.

  reply	other threads:[~2010-11-09  9:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-08 12:15 Why so many vm exits caused by ept violation lidong chen
2010-11-08 14:01 ` Avi Kivity
2010-11-08 16:29   ` lidong chen
2010-11-09  7:37     ` lidong chen
2010-11-09  7:45       ` Gleb Natapov
2010-11-09  9:04         ` lidong chen
2010-11-09  9:27           ` Gleb Natapov [this message]
2010-11-09 10:24             ` lidong chen
2010-11-09 11:24               ` Gleb Natapov
2010-11-10  7:09                 ` lidong chen
2010-11-10  8:26                   ` Avi Kivity
2010-11-15  4:34                     ` lidong chen
2010-11-15  6:40                       ` lidong chen
2010-11-15  7:24                         ` lidong chen
2010-11-15  9:09                           ` Avi Kivity
2010-11-15 12:39                             ` lidong chen
2010-11-15 12:44                               ` lidong chen
2010-11-16 13:35                                 ` lidong chen

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=20101109092727.GL9036@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=chen.lidong.kernel@gmail.com \
    --cc=kvm@vger.kernel.org \
    /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