public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: Out of sync shadow core breaks Hurd
Date: Tue, 25 Nov 2008 17:52:06 +0100	[thread overview]
Message-ID: <20081125165206.GA9267@hall.aurel32.net> (raw)
In-Reply-To: <20081125095717.GB23072@volta.aurel32.net>

On Tue, Nov 25, 2008 at 10:57:17AM +0100, Aurelien Jarno wrote:
> On Thu, Nov 20, 2008 at 10:48:21AM +0100, Marcelo Tosatti wrote:
> > Hi Aurelien,
> Hi,
> 
> > On Wed, Nov 12, 2008 at 08:00:37PM +0100, Aurelien Jarno wrote:
> > > Hi,
> > > 
> > > Starting with kvm-76 (and including kvm-79), Hurd does not boot anymore
> > > under KVM. The ext2fs translator issues a strange error message:
> > > 
> > > | Hurd server bootstrap: ext2fs.static[device:hd0s3] execext2fs.static: /build/bui
> > > | ldd/hurd-20080607/build-tree/hurd/ext2fs/dir.c:494: dirscanblock: Assertion `dp-
> > > | >dn->dirents[idx] == -1 || dp->dn->dirents[idx] == nentries' failed.           -
> > > | >dn->dirents[idx] == -1 || dp->dn->dirents[idx] == nentries' failed.
> > > 
> > > Bisecting the problem, I have found that it comes from this patch:
> > > 
> > > | 641fb03992b20aa640781a245f6b7136f0b845e4 is first bad commit
> > > | commit 641fb03992b20aa640781a245f6b7136f0b845e4
> > > | Author: Marcelo Tosatti <mtosatti@redhat.com>
> > > | Date:   Tue Sep 23 13:18:39 2008 -0300
> > > | 
> > > |     KVM: MMU: out of sync shadow core v2
> > > | 
> > > |     Allow guest pagetables to go out of sync.
> > > | 
> > > |     Signed-off-by: Marcelo Tosatti <mtosatti@redhat.com>
> > > |     Signed-off-by: Avi Kivity <avi@redhat.com>
> > > 
> > > The problem can be workarounded loading the kvm module with 
> > > oos_shadow=0.
> > > 
> > > The easiest way to reproduce the problem is to download a ready to use
> > > Hurd image [1]. The error message from the ext2fs translator is not
> > > exactly the same, but it still fails.
> > 
> > It seems Hurd does not always explicitly flush the TLB via cr0/cr3/cr4
> > writes or invlpg after updating pagetables. Debugging shows that OOS is
> > properly syncing the sptes wrt the guest pagetables, and that all pages
> > are synced before guest re-entry on TLB flush exits.
> 

Looking more precisely at the code, Hurd (actually GNU Mach) flushes the
TLB via cr3, but just *before* updating the pagetables. I have no idea
why it is done that way, but it seems to be correct given the way the
Intel MMU works. However, it fails to comply with the recommendations
from Intel ("5.2 Recommended Invalidation"), which if I understand 
correctly, have been taken as a basis for implementing out of sync 
shadow.

I have confirmed that by patching the GNU Mach code so that TLB are
flushed before and after modifying pagetables.

-- 
  .''`.  Aurelien Jarno	            | GPG: 1024D/F1BCDB73
 : :' :  Debian developer           | Electrical Engineer
 `. `'   aurel32@debian.org         | aurelien@aurel32.net
   `-    people.debian.org/~aurel32 | www.aurel32.net

      reply	other threads:[~2008-11-25 16:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 19:00 Out of sync shadow core breaks Hurd Aurelien Jarno
2008-11-15 12:15 ` Marcelo Tosatti
2008-11-20  9:48 ` Marcelo Tosatti
2008-11-25  9:57   ` Aurelien Jarno
2008-11-25 16:52     ` Aurelien Jarno [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=20081125165206.GA9267@hall.aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.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