From: "Michael S. Tsirkin" <mst@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Igor Mammedov" <imammedo@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH 0/7 RESEND] target-i386: Simplify kvm_cpu_fill_host() and kvm_check_features_against_host()
Date: Mon, 20 Jan 2014 22:39:23 +0200 [thread overview]
Message-ID: <20140120203923.GD14528@redhat.com> (raw)
In-Reply-To: <20140120183656.GF24353@otherpad.lan.raisama.net>
On Mon, Jan 20, 2014 at 04:36:56PM -0200, Eduardo Habkost wrote:
> On Mon, Jan 20, 2014 at 02:41:07PM -0200, Eduardo Habkost wrote:
> > Resend of series submitted on 24 November 2013, that didn't get any reply. Only
> > change is a trivial conflict on patch 7/7.
>
> Question: which tree is the most appropriate to get this in? qom-cpu?
> kvm?
Either kvm or my pc tree.
Seems unrelated to qom.
Paolo - want to review and take this?
>
> >
> > This series simplifies kvm_cpu_fill_host() and
> > kvm_check_features_against_host() to simply use FeatureWord & feature_word_info
> > loops to fill/check feature words.
> >
> > The initial motivation for this was to avoid hacks involving the "host" CPU
> > class on the forthcoming conversion of CPU models to be X86CPU subclasses.
> > Instead of requiring the kvm_arch_get_supported_cpuid() results to be stored in
> > the class struct for "host" (thus requiring KVM initialization hacks).
> >
> > Eduardo Habkost (7):
> > target-i386: kvm_cpu_fill_host(): Kill unused code
> > target-i386: kvm_cpu_fill_host(): No need to check level
> > target-i386: kvm_cpu_fill_host(): No need to check CPU vendor
> > target-i386: kvm_cpu_fill_host(): No need to check xlevel2
> > target-i386: kvm_cpu_fill_host(): Set all feature words at end of
> > function
> > target-i386: kvm_cpu_fill_host(): Fill feature words in a loop
> > target-i386: kvm_check_features_against_host(): Kill feature word
> > array
> >
> > target-i386/cpu.c | 89 +++++++++++++------------------------------------------
> > 1 file changed, 20 insertions(+), 69 deletions(-)
> >
> > --
> > 1.8.4.2
> >
> >
>
> --
> Eduardo
next prev parent reply other threads:[~2014-01-20 20:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-20 16:41 [Qemu-devel] [PATCH 0/7 RESEND] target-i386: Simplify kvm_cpu_fill_host() and kvm_check_features_against_host() Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 1/7] target-i386: kvm_cpu_fill_host(): Kill unused code Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 2/7] target-i386: kvm_cpu_fill_host(): No need to check level Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 3/7] target-i386: kvm_cpu_fill_host(): No need to check CPU vendor Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 4/7] target-i386: kvm_cpu_fill_host(): No need to check xlevel2 Eduardo Habkost
2014-01-20 21:16 ` Andreas Färber
2014-01-21 10:52 ` Paolo Bonzini
2014-01-20 16:41 ` [Qemu-devel] [PATCH 5/7] target-i386: kvm_cpu_fill_host(): Set all feature words at end of function Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 6/7] target-i386: kvm_cpu_fill_host(): Fill feature words in a loop Eduardo Habkost
2014-01-20 16:41 ` [Qemu-devel] [PATCH 7/7 v2] target-i386: kvm_check_features_against_host(): Kill feature word array Eduardo Habkost
2014-01-20 18:36 ` [Qemu-devel] [PATCH 0/7 RESEND] target-i386: Simplify kvm_cpu_fill_host() and kvm_check_features_against_host() Eduardo Habkost
2014-01-20 20:39 ` Michael S. Tsirkin [this message]
2014-01-20 21:07 ` Andreas Färber
2014-01-20 22:51 ` Michael S. Tsirkin
2014-01-21 10:03 ` Paolo Bonzini
2014-01-21 10:20 ` Andreas Färber
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=20140120203923.GD14528@redhat.com \
--to=mst@redhat.com \
--cc=afaerber@suse.de \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--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).