public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andre Przywara <andre.przywara@amd.com>
To: Avi Kivity <avi@redhat.com>
Cc: Jerry Geis <geisj@pagestation.com>, kvm@vger.kernel.org
Subject: Re: kvm guest for 486 sx
Date: Wed, 8 Jul 2009 13:04:48 +0200	[thread overview]
Message-ID: <4A547D50.70501@amd.com> (raw)
In-Reply-To: <4A534C46.3040603@redhat.com>

Avi Kivity wrote:
> On 07/07/2009 04:15 PM, Jerry Geis wrote:
>>>> Notice FPU indicates yes and I requested -fpu on the command line.
>>>
>>> I think it detects the host fpu as a 487 coprocessor.  Anything in 
>>> dmesg about it?  Note there's no fpu in the flags: line.
>>>
>>> That's a kvm kernel bug.
>>>
>>>> also is this a 486 as it says AMD?
>>>
>>> You can override it if you like, -cpu 486,vendor=AuthenticAMD (I think).
>>>
>>
>> Sorry - I thought the " -cpu 486,-fpu " was the way to turn off the fpu.
>> I 'm trying to emulute a 486 sx that has no fpu.
> 
> I thought so too, but in fact it emulates a 486sx+487.
-fpu does not help here, as the injected 486 CPUID limits the level to 
0, so effectively no other leaf than leaf 0 is checked by the guest. 
That's why the FPU bit, which is 0000_0001.EDX:0, is not honored.
I bumped up the level to 1 and set the model to 2, which should mimic a 
later 486SX chip, together with -fpu Linux (2.6.21) still insisted on 
fpu: yes (probably determined by probing FPU instructions).
 >  We can make it
> emulate a 486sx without a 487, but that will take a kernel patch.
What are you thinking of? Forcing CR0.EM to 1 (and don't let the guest 
change it), then inject #NM into the guest?

Regards,
Andre.

-- 
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany
Tel: +49 351 448 3567 12
----to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy; Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632


  parent reply	other threads:[~2009-07-08 11:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-06 19:58 kvm guest for 486 sx Jerry Geis
2009-07-07  9:54 ` Avi Kivity
2009-07-07 12:06   ` Jerry Geis
2009-07-07 12:17     ` Avi Kivity
2009-07-07 12:31       ` Jerry Geis
2009-07-07 12:36       ` Jerry Geis
2009-07-07 12:50         ` Avi Kivity
2009-07-07 13:15           ` Jerry Geis
2009-07-07 13:23             ` Avi Kivity
2009-07-07 14:58               ` Jerry Geis
2009-07-07 15:38                 ` Avi Kivity
2009-07-07 23:35                   ` Jerry Geis
2009-07-08 11:04               ` Andre Przywara [this message]
2009-07-08 11:25                 ` Avi Kivity
2009-07-07 12:19     ` Gleb Natapov

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=4A547D50.70501@amd.com \
    --to=andre.przywara@amd.com \
    --cc=avi@redhat.com \
    --cc=geisj@pagestation.com \
    --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