From: Alistair John Strachan <alistair@devzero.co.uk>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1, KVM-AMD problem
Date: Mon, 30 Jul 2007 18:00:55 +0100 [thread overview]
Message-ID: <200707301800.55671.alistair@devzero.co.uk> (raw)
In-Reply-To: <46ADE0DD.1030505@qumranet.com>
On Monday 30 July 2007 14:00:13 Avi Kivity wrote:
> How about the attached patch? (I haven't yet tried to reproduce, but
> this can cause an AMD-only oops).
This seems to have fixed the problem. Thanks Avi.
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
next prev parent reply other threads:[~2007-07-30 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-28 17:55 2.6.23-rc1, KVM-AMD problem Alistair John Strachan
2007-07-29 8:16 ` Avi Kivity
2007-07-29 11:29 ` Alistair John Strachan
2007-07-29 11:34 ` Avi Kivity
2007-07-29 13:44 ` Alistair John Strachan
2007-07-29 13:47 ` Avi Kivity
2007-07-29 14:10 ` Alistair John Strachan
2007-07-30 13:00 ` Avi Kivity
2007-07-30 17:00 ` Alistair John Strachan [this message]
2007-07-30 17:05 ` Avi Kivity
2007-08-04 13:17 ` Prakash Punnoor
2007-08-04 14:24 ` Alistair John Strachan
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=200707301800.55671.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@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