From: "H. Peter Anvin" <hpa@zytor.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Orit Wasserman" <owasserm@redhat.com>,
"Andreas Färber" <afaerber@suse.de>,
"Anthony Liguori" <anthony@codemonkey.ws>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC PATCH 1/3] target-i386: Add 486sx, old486, and old486sx CPU models
Date: Mon, 25 Mar 2013 13:56:41 -0700 [thread overview]
Message-ID: <5150BA09.7070809@zytor.com> (raw)
In-Reply-To: <20130325205636.GK8494@otherpad.lan.raisama.net>
On 03/25/2013 01:56 PM, Eduardo Habkost wrote:
>
>>
>> It needs to be possible to fix bugs....
>
> It is possible to fix them today: just write a compat function or add a
> global variable that is handled by cpu_x86_init(), and call it from the
> pc-1.3 machine-type init function. See disable_kvm_pv_eoi() and
> enable_compat_apic_id_mode(), for example.
>
> The difference is that this will be much easier once we introduce the
> static properties: then you just need to add the compat property values
> to the compat_props field on the machine-type struct.
>
It sounds like this is underway, and since the priority for the 486 bit
is very low it is better for that bit to just wait.
-hpa
next prev parent reply other threads:[~2013-03-25 20:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1362017554-1260-1-git-send-email-hpa@zytor.com>
2013-03-24 5:06 ` [Qemu-devel] [RFC PATCH 1/3] target-i386: Add 486sx, old486, and old486sx CPU models H. Peter Anvin
2013-03-25 9:06 ` Paolo Bonzini
2013-03-25 9:23 ` Andreas Färber
[not found] ` <1362017554-1260-3-git-send-email-hpa@zytor.com>
2013-03-25 9:05 ` [Qemu-devel] [RFC PATCH 3/3] mc146818rtc: export the timezone information Paolo Bonzini
2013-03-25 15:47 ` H. Peter Anvin
2013-03-25 15:51 ` Paolo Bonzini
2013-03-25 9:39 ` [Qemu-devel] [RFC PATCH 1/3] target-i386: Add 486sx, old486, and old486sx CPU models Andreas Färber
2013-03-25 15:15 ` Igor Mammedov
2013-03-25 18:44 ` H. Peter Anvin
2013-03-25 19:05 ` Eduardo Habkost
2013-03-25 20:45 ` H. Peter Anvin
2013-03-25 20:56 ` Eduardo Habkost
2013-03-25 20:56 ` H. Peter Anvin [this message]
2014-01-07 5:53 ` H. Peter Anvin
2014-01-07 9:08 ` Igor Mammedov
2013-03-25 20:47 ` H. Peter Anvin
2013-03-25 19:01 ` Eduardo Habkost
[not found] ` <1362017554-1260-2-git-send-email-hpa@zytor.com>
2013-03-28 19:15 ` [Qemu-devel] [RFC PATCH 2/3] target-i386: Raise #UD on accessing non-existent control registers Aurelien Jarno
2013-03-28 19:15 ` [Qemu-devel] [RFC PATCH 1/3] target-i386: Add 486sx, old486, and old486sx CPU models Aurelien Jarno
2013-03-28 20:02 ` H. Peter Anvin
2013-03-28 20:12 ` H. Peter Anvin
2013-03-29 5:10 ` Rob Landley
2013-03-29 5:25 ` H. Peter Anvin
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=5150BA09.7070809@zytor.com \
--to=hpa@zytor.com \
--cc=afaerber@suse.de \
--cc=anthony@codemonkey.ws \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=owasserm@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).