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] [RFC 0/6] x86 CPU subclasses, v4
Date: Fri,  4 Jan 2013 17:56:16 -0200	[thread overview]
Message-ID: <1357329382-20944-1-git-send-email-ehabkost@redhat.com> (raw)

This is a new RFC for the x86 CPU subclasses. This version handles the "host"
subclass differently, and I believe this made the code much simpler.

However, a few tricks were necessary:

 - To keep the "default_kvm_features" compat functions working (this shouldn't
   be necessary once we start using global properties for the compat code).
 - For the vendor property setting (because it depends on a kvm_enabled() check,
   that can't be made on class_init). I don't know how we will be able to
   convert that logic using global properties/defaults in the future.
 - To keep the original model names in the "-cpu ?" output, for compatibility.

This series depends on multiple series:
 - pc-1.4 kvm_mmu_opt disable series I sent today;
 - -cpu "enforce" fix series I sent today;
 - A experimental rebased version of Igor's "wave 2" x86 CPU init cleanup.

Because of the tricky dependencies, I recommend you use the git tree for testing:
  git://github.com/ehabkost/qemu-hacks.git x86-cpu-model-classes.RFC.v4
  https://github.com/ehabkost/qemu-hacks/tree/x86-cpu-model-classes.RFC.v4

Eduardo Habkost (6):
  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: CPU model subclasses

 include/sysemu/kvm.h  |    3 +
 target-i386/cpu-qom.h |   26 +
 target-i386/cpu.c     | 1548 ++++++++++++++++++++++++++++++-------------------
 target-i386/cpu.h     |    4 +-
 target-i386/helper.c  |   26 +-
 target-i386/kvm.c     |    2 +
 6 files changed, 988 insertions(+), 621 deletions(-)

-- 
1.7.11.7

             reply	other threads:[~2013-01-04 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-04 19:56 Eduardo Habkost [this message]
2013-01-04 19:56 ` [Qemu-devel] [RFC 1/6] target-i386: Move CPU object creation to cpu.c Eduardo Habkost
2013-01-04 19:56 ` [Qemu-devel] [RFC 2/6] target-i386: Make cpu_x86_create() get Error argument Eduardo Habkost
2013-01-04 19:56 ` [Qemu-devel] [RFC 3/6] target-i386: Simplify cpu_x86_find_by_name() logic Eduardo Habkost
2013-01-04 19:56 ` [Qemu-devel] [RFC 4/6] target-i386: Set feature string parsing results directly on CPU object Eduardo Habkost
2013-01-04 19:56 ` [Qemu-devel] [RFC 5/6] target-i386: Move kvm_features/hypervisor initialization to cpu_x86_find_by_name() Eduardo Habkost
2013-01-04 19:56 ` [Qemu-devel] [RFC 6/6] target-i386: CPU model subclasses Eduardo Habkost
2013-01-04 22:08   ` Eduardo Habkost
2013-01-04 22:07 ` [Qemu-devel] [RFC 0/6] x86 CPU subclasses, v4 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=1357329382-20944-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).