From: Joerg Roedel <joro@8bytes.org>
To: Avi Kivity <avi@qumranet.com>
Cc: Joerg Rodel <joerg.roedel@amd.com>,
kvm@vger.kernel.org, stable@kernel.org,
Alexander Graf <agraf@suse.de>
Subject: Re: [PATCH] KVM: SVM: fix random segfaults with NPT enabled
Date: Wed, 27 Aug 2008 17:32:25 +0200 [thread overview]
Message-ID: <20080827153225.GA3801@8bytes.org> (raw)
In-Reply-To: <48B57104.7060001@qumranet.com>
On Wed, Aug 27, 2008 at 06:21:40PM +0300, Avi Kivity wrote:
> Joerg Rodel wrote:
>
>
>
> >>hm. tbench doesn't allocate memory, so there shouldn't be any npt
> >>faults. I don't see how this can make a difference.
> >>
> >
> >
>
> I reproduced it. There are a few npt faults as the guest has not
> touched all of memory yet. If I force it to touch all of memory (dd <
> /dev/hda), the problem appears to go away.
>
> >Base for the fix was this bugreport:
> >
> >http://sourceforge.net/tracker/index.php?func=detail&aid=2019053&group_id=180599&atid=893831
> >
> >We found out that the same crash occur on long running compile
> >workloads and that stale tlb-entries cause it. Until we find the real
> >location of the missing tlb flush in the mmu code, i think its best to
> >flush the TLB every time the mapping/unmapping code for the nested page
> >table is executed. This fixes at least the crashes in the guest and has
> >only minimal performance impact.
> >
>
> I'd like to try and find out what the problem is exactly. Otherwise we
> may be only narrowing the window, not closing it.
Agreed. The fix I sent is only meant to be temporary until we find the
real root cause of the problem.
Joerg
next prev parent reply other threads:[~2008-08-27 15:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 12:18 [PATCH] KVM: SVM: fix random segfaults with NPT enabled Joerg Rodel
2008-08-27 13:11 ` Avi Kivity
2008-08-27 13:53 ` Joerg Rodel
2008-08-27 15:21 ` Avi Kivity
2008-08-27 15:32 ` Joerg Roedel [this message]
2008-08-27 13:53 ` Avi Kivity
2008-08-27 13:57 ` Joerg Rodel
2008-08-27 15:22 ` Avi Kivity
2008-08-27 15:35 ` Joerg Roedel
2008-08-27 15:50 ` Avi Kivity
2008-08-27 16:27 ` Joerg Rodel
2008-08-27 16:49 ` Avi Kivity
2008-08-27 16:59 ` Avi Kivity
2008-08-28 14:58 ` Joerg Rodel
2008-08-28 15:15 ` Avi Kivity
2008-08-28 15:19 ` Joerg Roedel
2008-08-28 15:47 ` Avi Kivity
2008-08-28 15:29 ` Avi Kivity
2008-08-28 15:58 ` Joerg Roedel
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=20080827153225.GA3801@8bytes.org \
--to=joro@8bytes.org \
--cc=agraf@suse.de \
--cc=avi@qumranet.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=stable@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