qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Igor Mammedov" <imammedo@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/9] x86 CPU subclasses
Date: Fri, 28 Dec 2012 18:33:57 -0200	[thread overview]
Message-ID: <1356726846-10637-1-git-send-email-ehabkost@redhat.com> (raw)

This is basically a x86 CPU subclasses RFC, preceded by some changes that I
would like to include even if this particular approach to the x86 CPU subclasses
doesn't get accepted (so the first patches are marked as PATCH instead of RFC).

The main differences from the RFC sent by Andreas previously is:
 - As we can't guarantee that class_init will get called only after KVM is
   initialized, the class for "host" initializes everything inside instance_init
 - Because of that difference, there's a separate base class for the predefined
   CPU models (TYPE_X86_PREDEF_CPU), that won't be used for TYPE_X86_HOST_CPU.
 - Instead of moving all x86_def_t fields inline to X86CPUClass, I am embedding
   x86_def_t inside PredefX86CPUClass, so kvm_cpu_fill_host() can keep getting
   x86_def_t* as argument, so they can still be used by
   kvm_check_features_against_host() _and_ by the -cpu "host" initialization
   code.

This series is based on:
 - [PATCH 0/2] Fixes for -cpu host KVM/SVM feature initialization
   Message-Id: <1356719854-16401-1-git-send-email-ehabkost@redhat.com>
 - [PATCH 00/20 v4] x86 CPU cleanup (wave 2)
   Message-Id: <1356724895-24118-1-git-send-email-imammedo@redhat.com>

Git tree for testing:
  git://github.com/ehabkost/qemu-hacks.git x86-cpu-model-classes.RFC.v3
  https://github.com/ehabkost/qemu-hacks/tree/x86-cpu-model-classes.RFC.v3


Eduardo Habkost (9):
  target-i386: Move CPU object creation to cpu.c
  target-i386: Make cpu_x86_create() get Error argument
  target-i386: Simplify cpu_x86_find_by_name() logic
  target-i386: Set feature string parsing results directly on CPU
    object
  target-i386: Move kvm_features/hypervisor initialization to
    cpu_x86_find_by_name()
  target-i386: Move CPU creation code to model name lookup function
  target-i386: CPU subclass for -cpu "host"
  target-i386: CPU subclasses for predefined CPU models
  target-i386: Unify CPU object creation on x86_cpu_create_from_name()

 target-i386/cpu-qom.h |   1 +
 target-i386/cpu.c     | 785 ++++++++++++++++++++++++++++++++++++++------------
 target-i386/cpu.h     |   4 +-
 target-i386/helper.c  |  26 +-
 4 files changed, 614 insertions(+), 202 deletions(-)

-- 
1.7.11.7

             reply	other threads:[~2012-12-28 20:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-28 20:33 Eduardo Habkost [this message]
2012-12-28 20:33 ` [Qemu-devel] [PATCH 1/9] target-i386: Move CPU object creation to cpu.c Eduardo Habkost
2012-12-28 20:33 ` [Qemu-devel] [PATCH 2/9] target-i386: Make cpu_x86_create() get Error argument Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [PATCH 3/9] target-i386: Simplify cpu_x86_find_by_name() logic Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 4/9] target-i386: Set feature string parsing results directly on CPU object Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 5/9] target-i386: Move kvm_features/hypervisor initialization to cpu_x86_find_by_name() Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 6/9] target-i386: Move CPU creation code to model name lookup function Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 7/9] target-i386: CPU subclass for -cpu "host" Eduardo Habkost
2013-01-02 19:00   ` Igor Mammedov
2013-01-02 20:07     ` Igor Mammedov
2013-01-02 20:20       ` Eduardo Habkost
2013-01-02 20:16     ` Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 8/9] target-i386: CPU subclasses for predefined CPU models Eduardo Habkost
2012-12-28 20:34 ` [Qemu-devel] [RFC 9/9] target-i386: Unify CPU object creation on x86_cpu_create_from_name() Eduardo Habkost

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=1356726846-10637-1-git-send-email-ehabkost@redhat.com \
    --to=ehabkost@redhat.com \
    --cc=afaerber@suse.de \
    --cc=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).