qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: qemu-devel@nongnu.org
Cc: "Liu Jinsong" <jinsong.liu@intel.com>,
	"Lai Jiangshan" <laijs@cn.fujitsu.com>,
	"Jan Kiszka" <jan.kiszka@siemens.com>,
	"Vasilis Liaskovitis" <vasilis.liaskovitis@profitbricks.com>,
	"Anthony Liguori" <anthony@codemonkey.ws>,
	"Igor Mammedov" <imammedo@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>,
	"Eduardo Habkost" <ehabkost@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/4] QOM'ify x86 CPU, part 1
Date: Tue,  3 Apr 2012 02:05:07 +0200	[thread overview]
Message-ID: <1333411511-10139-1-git-send-email-afaerber@suse.de> (raw)

Hello,

This series strips down x86 CPU QOM'ification to the bare minimum,
leaving out subclasses for builtin or external CPU models.
It is ordered after the s390x conversion but is independent of it, again
due to alphabetical ordering, so that it could be applied right away now.

While I haven't seen any follow-up patches for X86CPU hotplug yet,
patch 2 is the one that allows to either use it as a child<> of a device
or to put TYPE_CPU directly onto some qdev bus for CONFIG_SOFTMMU.

Available from:
git://github.com/afaerber/qemu-cpu.git qom-cpu-x86.v2
https://github.com/afaerber/qemu-cpu/commits/qom-cpu-x86.v2

Regards,
Andreas

Cc: Anthony Liguori <anthony@codemonkey.ws>
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Liu Jinsong <jinsong.liu@intel.com>
Cc: Lai Jiangshan <laijs@cn.fujitsu.com>
Cc: Vasilis Liaskovitis <vasilis.liaskovitis@profitbricks.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>

v1 -> v2:
* Move file rename to its own patch.
* Set diff.renames to true to force rename detection for cpu.c.
* Postpone TYPE_X86_CPU subclasses and split off reset and initfn conversion.

Andreas Färber (4):
  target-i386: Rename cpuid.c
  target-i386: QOM'ify CPU
  target-i386: QOM'ify CPU init
  target-i386: QOM'ify CPU reset

 Makefile.target                |    2 +-
 target-i386/cpu-qom.h          |   71 +++++++++++++++++++++
 target-i386/{cpuid.c => cpu.c} |  134 ++++++++++++++++++++++++++++++++++++++++
 target-i386/cpu.h              |    3 +-
 target-i386/helper.c           |  100 ++----------------------------
 5 files changed, 213 insertions(+), 97 deletions(-)
 create mode 100644 target-i386/cpu-qom.h
 rename target-i386/{cpuid.c => cpu.c} (92%)

-- 
1.7.7

             reply	other threads:[~2012-04-03  0:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-03  0:05 Andreas Färber [this message]
2012-04-03  0:05 ` [Qemu-devel] [PATCH v2 1/4] target-i386: Rename cpuid.c Andreas Färber
2012-04-03  0:05 ` [Qemu-devel] [PATCH v2 2/4] target-i386: QOM'ify CPU Andreas Färber
2012-04-03  0:05 ` [Qemu-devel] [PATCH v2 3/4] target-i386: QOM'ify CPU init Andreas Färber
2012-04-03  0:05 ` [Qemu-devel] [PATCH v2 4/4] target-i386: QOM'ify CPU reset 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=1333411511-10139-1-git-send-email-afaerber@suse.de \
    --to=afaerber@suse.de \
    --cc=anthony@codemonkey.ws \
    --cc=ehabkost@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=jinsong.liu@intel.com \
    --cc=laijs@cn.fujitsu.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vasilis.liaskovitis@profitbricks.com \
    /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).