From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Ryan Harper <ryanh@us.ibm.com>, kvm@vger.kernel.org
Subject: Re: BUG at mmu.c:615 from localhost migration using ept+hugetlbfs
Date: Wed, 10 Jun 2009 11:08:14 +0300 [thread overview]
Message-ID: <4A2F69EE.9080503@redhat.com> (raw)
In-Reply-To: <4A2E920E.8010703@redhat.com>
Avi Kivity wrote:
>
> Not really. One thing, migration should transition the shadow
> pagetables from large pages to small ones, maybe that bit is broken.
>
> Maybe we're looking at a largepage spte and interpreting it as a
> normal L2 spte, and interpreting a guest page as the L1 spt.
I tried to find where we drop the mmu (or at least large sptes for the
slot) when we enable dirty logging, and failed. Maybe
remove_write_access() is sufficient.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2009-06-10 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-29 16:43 BUG at mmu.c:615 from localhost migration using ept+hugetlbfs Ryan Harper
2009-06-09 16:40 ` Marcelo Tosatti
2009-06-09 16:47 ` Avi Kivity
2009-06-10 8:08 ` Avi Kivity [this message]
2009-06-10 12:10 ` Marcelo Tosatti
2009-06-09 18:31 ` Ryan Harper
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=4A2F69EE.9080503@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=ryanh@us.ibm.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