From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC 6/6] i386: -cpu help: remove reference to specific CPUID leaves/registers
Date: Wed, 5 Sep 2012 13:47:30 +0200 [thread overview]
Message-ID: <20120905134730.6da48739@nial.usersys.redhat.com> (raw)
In-Reply-To: <1345226022-21654-7-git-send-email-ehabkost@redhat.com>
On Fri, 17 Aug 2012 14:53:42 -0300
Eduardo Habkost <ehabkost@redhat.com> wrote:
> The -cpu configuration interface is based on a list of feature names or
> properties, on a single namespace, so there's no need to mention on
> which CPUID leaf/register each flag is located.
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> target-i386/cpu.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/target-i386/cpu.c b/target-i386/cpu.c
> index a71c2fc..0a03c80 100644
> --- a/target-i386/cpu.c
> +++ b/target-i386/cpu.c
> @@ -1297,13 +1297,13 @@ void x86_cpu_list(FILE *f, fprintf_function
> cpu_fprintf) }
> (*cpu_fprintf)(f, "\nRecognized CPUID flags:\n");
> listflags(buf, sizeof(buf), (uint32_t)~0, feature_name, 1);
> - (*cpu_fprintf)(f, " f_edx: %s\n", buf);
> + (*cpu_fprintf)(f, " %s\n", buf);
> listflags(buf, sizeof(buf), (uint32_t)~0, ext_feature_name, 1);
> - (*cpu_fprintf)(f, " f_ecx: %s\n", buf);
> + (*cpu_fprintf)(f, " %s\n", buf);
> listflags(buf, sizeof(buf), (uint32_t)~0, ext2_feature_name, 1);
> - (*cpu_fprintf)(f, " extf_edx: %s\n", buf);
> + (*cpu_fprintf)(f, " %s\n", buf);
> listflags(buf, sizeof(buf), (uint32_t)~0, ext3_feature_name, 1);
> - (*cpu_fprintf)(f, " extf_ecx: %s\n", buf);
> + (*cpu_fprintf)(f, " %s\n", buf);
> }
>
> CpuDefinitionInfoList *qmp_query_cpu_definitions(Error **errp)
If you are removing this ones, why do you leave:
if (dump) {
...
(*cpu_fprintf)(f, " feature_edx %08x (%s)\n", def->features,
....
next prev parent reply other threads:[~2012-09-05 11:47 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 [this message]
2012-08-20 12:02 ` [Qemu-devel] [RFC 0/6] i386: CPU: remove duplicate feature names Igor Mammedov
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=20120905134730.6da48739@nial.usersys.redhat.com \
--to=imammedo@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).