public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Xiao Guangrong <xiaoguangrong@linux.vnet.ibm.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: kvm@vger.kernel.org
Subject: Re: [Bug 54061] guest panic after live migration
Date: Mon, 25 Feb 2013 16:26:17 +0800	[thread overview]
Message-ID: <512B2029.1090009@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130220080616.A0DCA11FB82@bugzilla.kernel.org>

On 02/20/2013 04:06 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=54061
> 
> 
> 
> 
> 
> --- Comment #2 from Jay Ren <yongjie.ren@intel.com>  2013-02-20 08:06:16 ---
> Marcleo,
> 
> yes, after reverting that commit "caf6900f2d8", live-migration can work fine.
> 

Sorry for the wrong patch and the bug is: the fast page fault path
can make large-spte writeable without probably set dirty bitmap for
all small pages.

Two ways to fix these:
1): covert the large-spte to small sptes and wirte-protect them, then
    no readonly large-spte exists.

2): only allow fast page fault to fix #PF on small spte.

Seems the first way is better because the second way can cause useless
page table waking.


  reply	other threads:[~2013-02-25  8:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-19  3:05 [Bug 54061] New: guest panic after live migration bugzilla-daemon
2013-02-20  2:43 ` [Bug 54061] " bugzilla-daemon
2013-02-20  8:06 ` bugzilla-daemon
2013-02-25  8:26   ` Xiao Guangrong [this message]
2013-02-25  8:26 ` bugzilla-daemon
2013-03-01  7:33 ` bugzilla-daemon
2013-03-01  7:33 ` bugzilla-daemon
2013-03-01  7:34 ` bugzilla-daemon

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=512B2029.1090009@linux.vnet.ibm.com \
    --to=xiaoguangrong@linux.vnet.ibm.com \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --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