qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: "Eduardo Habkost" <ehabkost@redhat.com>,
	qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [qom-cpu PATCH 00/10] target-i386: Support check/enforce flags in TCG mode, too
Date: Fri, 28 Feb 2014 13:32:28 -0800	[thread overview]
Message-ID: <5311006C.40003@twiddle.net> (raw)
In-Reply-To: <1393618913-12411-1-git-send-email-ehabkost@redhat.com>

On 02/28/2014 12:21 PM, Eduardo Habkost wrote:
> This removes some duplication in the CPU feature checking and filtering code in
> cpu.c, and as a nice side-effect, will make the "check" and "enforce" flags work
> in TCG mode too.
> 
> Eduardo Habkost (10):
>   target-i386: Simplify reporting of unavailable features
>   target-i386: Merge feature filtering/checking functions
>   target-i386: Pass FeatureWord argument to
>     report_unavailable_features()
>   target-i386: Isolate KVM-specific code on CPU feature filtering logic
>   target-i386: Make TCG feature filtering more readable
>   target-i386: Filter FEAT_7_0_EBX TCG features too
>   target-i386: Filter KVM and 0xC0000001 features on TCG
>   target-i386: Define TCG_*_FEATURES earlier on cpu.c
>   target-i386: Loop-based feature word filtering in TCG mode
>   target-i386: Support check/enforce flags in TCG mode, too
> 
>  target-i386/cpu.c | 215 +++++++++++++++++++++++++++---------------------------
>  1 file changed, 107 insertions(+), 108 deletions(-)
> 

Reviewed-by: Richard Henderson <rth@twiddle.net>

r~

      parent reply	other threads:[~2014-02-28 21:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-28 20:21 [Qemu-devel] [qom-cpu PATCH 00/10] target-i386: Support check/enforce flags in TCG mode, too Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 01/10] target-i386: Simplify reporting of unavailable features Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 02/10] target-i386: Merge feature filtering/checking functions Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 03/10] target-i386: Pass FeatureWord argument to report_unavailable_features() Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 04/10] target-i386: Isolate KVM-specific code on CPU feature filtering logic Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 05/10] target-i386: Make TCG feature filtering more readable Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 06/10] target-i386: Filter FEAT_7_0_EBX TCG features too Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 07/10] target-i386: Filter KVM and 0xC0000001 features on TCG Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 08/10] target-i386: Define TCG_*_FEATURES earlier on cpu.c Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 09/10] target-i386: Loop-based feature word filtering in TCG mode Eduardo Habkost
2014-02-28 20:21 ` [Qemu-devel] [qom-cpu PATCH 10/10] target-i386: Support check/enforce flags in TCG mode, too Eduardo Habkost
2014-02-28 21:32 ` Richard Henderson [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=5311006C.40003@twiddle.net \
    --to=rth@twiddle.net \
    --cc=afaerber@suse.de \
    --cc=aurelien@aurel32.net \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=pbonzini@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).