All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: xming <xmingske@gmail.com>, Avi Kivity <avi@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: with kerenl 2.6.27, CONFIG_KVM_GUEST does not work
Date: Sat, 11 Oct 2008 15:04:36 -0300	[thread overview]
Message-ID: <20081011180436.GA13387@dmt.cnet> (raw)
In-Reply-To: <519a8b110810100911j2e8229a2mf86f770b724a1bc3@mail.gmail.com>

On Fri, Oct 10, 2008 at 06:11:08PM +0200, xming wrote:
> Kernel 2.6.27 + kvm-76 on the host really gives some performance boost here.
> but:
> 
> When running 2.6.27 compiled with CONFIG_KVM_GUEST=y in the guest, the guest
> won't start, lot's of segfaults (in the guest)  especially udev initializations.
> 
> unset CONFIG_KVM_GUEST=y, then the guest runs fine

Does the attached work for you?

Avi, do you have thoughts on how to proceed with pvmmu? Using hypercalls
instead of faults can still be beneficial (for the first write before
page goes out of sync, or for non-leaf tables which currently don't go
oos). But at the current state pvmmu should be slower in most loads.
Perhaps disable it?

KVM: MMU: sync root on paravirt TLB flush

The pvmmu TLB flush handler should request a root sync, similarly to
a native read-write CR3.

Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>

diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
index 79cb4a9..7e70e97 100644
--- a/arch/x86/kvm/mmu.c
+++ b/arch/x86/kvm/mmu.c
@@ -2747,6 +2747,7 @@ static int kvm_pv_mmu_write(struct kvm_vcpu *vcpu,
 static int kvm_pv_mmu_flush_tlb(struct kvm_vcpu *vcpu)
 {
 	kvm_x86_ops->tlb_flush(vcpu);
+	set_bit(KVM_REQ_MMU_SYNC, &vcpu->requests);
 	return 1;
 }
 

  reply	other threads:[~2008-10-11 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-10 16:11 with kerenl 2.6.27, CONFIG_KVM_GUEST does not work xming
2008-10-11 18:04 ` Marcelo Tosatti [this message]
2008-10-12 20:57   ` Held Bernhard
2008-10-14  6:49     ` Xavier Gnata
2008-10-14  7:16       ` Bernhard Held
2008-10-13 17:44   ` Al Tobey
2008-10-15  7:17     ` Xavier Gnata

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=20081011180436.GA13387@dmt.cnet \
    --to=mtosatti@redhat.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=xmingske@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.