From: Igor Mammedov <imammedo@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: aliguori@us.ibm.com, stefanha@linux.vnet.ibm.com,
gleb@redhat.com, jan.kiszka@siemens.com, mtosatti@redhat.com,
qemu-devel@nongnu.org, mdroth@linux.vnet.ibm.com,
blauwirbel@gmail.com, avi@redhat.com, pbonzini@redhat.com,
akong@redhat.com, lersek@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC 0/6] i386: CPU: remove duplicate feature names
Date: Mon, 20 Aug 2012 14:02:26 +0200 [thread overview]
Message-ID: <20120820140226.568ce6c5@thinkpad.mammed.net> (raw)
In-Reply-To: <1345226022-21654-1-git-send-email-ehabkost@redhat.com>
On Fri, 17 Aug 2012 14:53:36 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> The problem:
>
> - Some features are report at the same time on both CPUID[1].EDX and
> CPUID[8000_0001].EDX on AMD CPUs (e.g. fpu, tsc, msr, pae, mmx).
> - "-cpu <model>,+feature" should enable the bit only on CPUID[1] if
> it's not an AMD CPU, but it should enable the bit on both CPUID[1] and
> CPUID[8000_0001] if it's an AMD CPU.
> - The same should happen when implementing CPU properties: setting the
> property that enables a feature should set the duplicate CPUID[8000_0001].EDX
> bit only if CPU vendor is AMD.
>
> Reference: http://article.gmane.org/gmane.comp.emulators.qemu/166024
>
> The solution implemented by this series is:
> - On the CPU model table and while parsing CPU options/properties, set the bit
> only on CPUID[1] (the x86_def_t.features field).
> - When finishing initialization of the CPU cpuid fields, duplicate those
> feature bits on cpuid_ext2_features if and only if the CPU vendor is AMD.
>
> This series also removes the "cpudef" config support, to make this work easier
> (because the cpudef interface is based on low-level CPUID leaf+register
> specification, instead of a set of higher-level per-feature object properties).
>
> Eduardo Habkost (6):
> x86_cpudef_setup: coding style change
> i386: kill cpudef config section support
> i386: kvm: bit 10 of CPUID[8000_0001].EDX is reserved
> i386: kvm: use a #define for the set of alias feature bits
> i386: cpu: eliminate duplicate feature names
above 3 patches should go before cpu properties
> i386: -cpu help: remove reference to specific CPUID leaves/registers
>
> target-i386/cpu.c | 153 +++++++++++++-----------------------------------------
> target-i386/cpu.h | 12 +++++
> target-i386/kvm.c | 2 +-
> 3 files changed, 50 insertions(+), 117 deletions(-)
>
> --
> 1.7.11.2
>
>
--
Regards,
Igor
prev parent reply other threads:[~2012-08-20 12:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 17:53 [Qemu-devel] [RFC 0/6] i386: CPU: remove duplicate feature names Eduardo Habkost
2012-08-17 17:53 ` [Qemu-devel] [RFC 1/6] x86_cpudef_setup: coding style change Eduardo Habkost
2012-09-05 8:44 ` Igor Mammedov
2012-08-17 17:53 ` [Qemu-devel] [RFC 2/6] i386: kill cpudef config section support Eduardo Habkost
2012-08-20 10:51 ` Andreas Färber
2012-08-20 12:00 ` Igor Mammedov
2012-08-20 12:30 ` Eduardo Habkost
2012-09-05 9:09 ` Igor Mammedov
2012-09-05 9:39 ` Igor Mammedov
2012-09-06 17:55 ` Eduardo Habkost
2012-08-17 17:53 ` [Qemu-devel] [RFC 3/6] i386: kvm: bit 10 of CPUID[8000_0001].EDX is reserved Eduardo Habkost
2012-09-05 8:48 ` Igor Mammedov
2012-08-17 17:53 ` [Qemu-devel] [RFC 4/6] i386: kvm: use a #define for the set of alias feature bits Eduardo Habkost
2012-09-05 8:53 ` Igor Mammedov
2012-08-17 17:53 ` [Qemu-devel] [RFC 5/6] i386: cpu: eliminate duplicate feature names Eduardo Habkost
2012-08-17 17:53 ` [Qemu-devel] [RFC 6/6] i386: -cpu help: remove reference to specific CPUID leaves/registers Eduardo Habkost
2012-09-05 11:47 ` Igor Mammedov
2012-08-20 12:02 ` Igor Mammedov [this message]
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=20120820140226.568ce6c5@thinkpad.mammed.net \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=akong@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=gleb@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@linux.vnet.ibm.com \
/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).