LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Roland Dreier <rdreier@cisco.com>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org
Subject: Re: [kvm-devel] guest crash on 2.6.20-rc4
Date: Wed, 10 Jan 2007 13:33:47 -0800	[thread overview]
Message-ID: <ada8xgay3b7.fsf@cisco.com> (raw)
In-Reply-To: <45A40898.4040307@qumranet.com> (Avi Kivity's message of "Tue, 09 Jan 2007 23:26:48 +0200")

 >  	if (is_writeble_pte(*shadow_ent))
 > -		return 0;
 > +		return 1;

With this patch, it looks like my guest is surviving the load that
triggered the oops before.  So I think this fixes the issue I saw as well.
I assume you'll send this in for 2.6.20?

 - R.

  parent reply	other threads:[~2007-01-10 21:33 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-08 16:18 Roland Dreier
2007-01-09  8:53 ` [kvm-devel] " Avi Kivity
2007-01-09 21:26 ` Avi Kivity
2007-01-10 18:31   ` Roland Dreier
2007-01-10 21:33   ` Roland Dreier [this message]
2007-01-11  8:06     ` Avi Kivity

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=ada8xgay3b7.fsf@cisco.com \
    --to=rdreier@cisco.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [kvm-devel] guest crash on 2.6.20-rc4' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).