From: Avi Kivity <avi@qumranet.com>
To: Alistair John Strachan <alistair@devzero.co.uk>
Cc: kvm-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: 2.6.23-rc1, KVM-AMD problem
Date: Sun, 29 Jul 2007 11:16:43 +0300 [thread overview]
Message-ID: <46AC4CEB.9060401@qumranet.com> (raw)
In-Reply-To: <200707281855.41277.alistair@devzero.co.uk>
[-- Attachment #1: Type: text/plain, Size: 822 bytes --]
Alistair John Strachan wrote:
> Hi,
>
> I'm getting periodic oopses running KVM-33 on 2.6.23-rc1. Here is a digital
> photo of the oops. Alarmingly, a lot of the time it triple faults the machine
> and I don't get a chance to grab it. This time I was lucky, though.
>
> http://devzero.co.uk/~alistair/kvm-2.6.23-rc1.jpg
>
> Unfortunately, some of the oops text scrolled out of the screen. I will
> endeavour to reproduce the bug over serial console, but I can make no
> guarantees.
>
> The CPU is an AMD X2 BE-2350, chipset is AMD 690G.
>
>
If you are using the modules from 2.6.23-rc1, try upgrading to latest
-git, which contains a patch that might fix this problem. If you are
using the modules from kvm-33, try applying the attached patch.
--
error compiling committee.c: too many arguments to function
[-- Attachment #2: fix-0f-01.patch --]
[-- Type: text/x-patch, Size: 903 bytes --]
commit bfa6c62f98bd0602025d7b48e267d817082f5d07
Author: Aurelien Jarno <aurelien@aurel32.net>
Date: Wed Jul 25 10:19:54 2007 +0200
KVM: disable writeback for 0x0f 0x01 instructions.
0x0f 0x01 instructions (ie lgdt, lidt, smsw, lmsw and invlpg) does
not use writeback. This patch set no_wb=1 when emulating those
instructions.
This fixes a regression booting the FreeBSD kernel on AMD.
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Avi Kivity <avi@qumranet.com>
diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index 21ce977..cbbb9c5 100644
--- a/drivers/kvm/x86_emulate.c
+++ b/drivers/kvm/x86_emulate.c
@@ -1183,6 +1183,8 @@ pop_instruction:
twobyte_insn:
switch (b) {
case 0x01: /* lgdt, lidt, lmsw */
+ /* Disable writeback. */
+ no_wb = 1;
switch (modrm_reg) {
u16 size;
unsigned long address;
next prev parent reply other threads:[~2007-07-29 8:16 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 [this message]
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
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=46AC4CEB.9060401@qumranet.com \
--to=avi@qumranet.com \
--cc=alistair@devzero.co.uk \
--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