public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Mon, 30 Jul 2007 16:00:13 +0300	[thread overview]
Message-ID: <46ADE0DD.1030505@qumranet.com> (raw)
In-Reply-To: <200707291510.31731.alistair@devzero.co.uk>

[-- Attachment #1: Type: text/plain, Size: 1695 bytes --]

Alistair John Strachan wrote:
> On Sunday 29 July 2007 14:47:57 you wrote:
>   
>> Alistair John Strachan wrote:
>>     
>>> On Sunday 29 July 2007 12:34:28 you wrote:
>>> [snip]
>>>
>>>       
>>>>> Doesn't help, I still get the same crashes. I tried 2.6.22 again and
>>>>> it's rock solid by comparison.
>>>>>           
>>>> Do you mean, kvm-33 on top of 2.6.22, or the kvm modules from 2.6.22?
>>>> Please describe your configuration *exactly*.
>>>>         
>>> I'm using the kvm-33 *userspace* package (based on Debian's kvm-28
>>> packaging) and 2.6.23-rc1's KVM modules. I patched 2.6.23-rc1 with the
>>> patch you provided in your last email. So I'm not using -git HEAD.
>>>
>>> Maybe there's been additional necessary fixes to -git requiring me to
>>> update to HEAD? That wasn't clear from your last email.
>>>       
>> No,  that patch is the only potential fix post -rc1.  There are a few
>> other fixes there, but they are intended to avoid guest crashes, not
>> host crashes.
>>
>> What guest are you running?  Maybe I can reproduce it here.
>>     
>
> Right now, Windows XP. I'm pretty sure Linux (well, Debian Etch) works fine. I 
> could only get Windows to install with -no-acpi, but I run it with the 
> following (if this is at all useful):
>
> kvm -no-acpi -m 256 -hda $IMAGE -net nic -net tap,script=/etc/kvm/kvm-ifup
>
> Basically, the installer seems to work fine, but Windows seemed to have 
> problems after installing post-SP2 updates. Maybe that's why not everybody is 
> seeing it yet.
>
>   

How about the attached patch? (I haven't yet tried to reproduce, but 
this can cause an AMD-only oops).

-- 
error compiling committee.c: too many arguments to function


[-- Attachment #2: kvm-fix-debug-registers-on-amd.patch --]
[-- Type: text/x-patch, Size: 855 bytes --]

commit 80917728e43e248155c019f743655806b582b099
Author: Avi Kivity <avi@qumranet.com>
Date:   Mon Jul 30 15:56:36 2007 +0300

    KVM: x86 emulator: disable writeback for debug register instructions
    
    These are handled internally by the instruction.
    
    Signed-off-by: Avi Kivity <avi@qumranet.com>

diff --git a/drivers/kvm/x86_emulate.c b/drivers/kvm/x86_emulate.c
index 1a90ba0..2136da5 100644
--- a/drivers/kvm/x86_emulate.c
+++ b/drivers/kvm/x86_emulate.c
@@ -1222,11 +1222,13 @@ twobyte_insn:
 		}
 		break;
 	case 0x21: /* mov from dr to reg */
+		no_wb = 1;
 		if (modrm_mod != 3)
 			goto cannot_emulate;
 		rc = emulator_get_dr(ctxt, modrm_reg, &_regs[modrm_rm]);
 		break;
 	case 0x23: /* mov from reg to dr */
+		no_wb = 1;
 		if (modrm_mod != 3)
 			goto cannot_emulate;
 		rc = emulator_set_dr(ctxt, modrm_reg, _regs[modrm_rm]);

  reply	other threads:[~2007-07-30 13:00 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 [this message]
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=46ADE0DD.1030505@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