From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: zhugh.fnst@cn.fujitsu.com, tangchen@cn.fujitsu.com,
chen.fan.fnst@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Gu Zheng" <guz.fnst@cn.fujitsu.com>,
"Igor Mammedov" <imammedo@redhat.com>,
anshul.makkar@profitbricks.com,
"Andreas Färber" <afaerber@suse.de>
Subject: [Qemu-devel] [PATCH 0/6] target-i386: Remove side-effects from X86CPU::instance_init
Date: Thu, 5 Mar 2015 12:38:44 -0300 [thread overview]
Message-ID: <1425569930-6660-1-git-send-email-ehabkost@redhat.com> (raw)
To allow new code to ask the CPU classes for CPU model information and
allow QOM properties to be queried by qmp_device_list_properties(), we
need to be able to safely instantiate a X86CPU object without any
side-effects.
This series moves some code from x86_cpu_initfn() to x86_cpu_realizefn(), so
that QEMU global state is affected only if the CPU object is realized.
To make the patch moving the cpu_exec_init() call easier to review, the series
also includes a few small changes to simplify cpu_exec_init().
This series is based on my x86 tree, located at:
https://github.com/ehabkost/qemu.git x86
Eduardo Habkost (6):
cpu: No need to zero-initialize numa_node
cpu: Initialize breakpoint/watchpoint lists on cpu_common_initfn()
cpu: Reorder cpu->as and cpu->thread_id initialization
target-i386: Rename optimize_flags_init()
target-i386: Move TCG initialization to realize time
target-i386: Call cpu_exec_init() on realize
exec.c | 12 +++++-------
qom/cpu.c | 2 ++
target-i386/cpu.c | 16 ++++++++--------
target-i386/cpu.h | 2 +-
target-i386/translate.c | 2 +-
5 files changed, 17 insertions(+), 17 deletions(-)
--
2.1.0
next reply other threads:[~2015-03-05 15:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 15:38 Eduardo Habkost [this message]
2015-03-05 15:38 ` [Qemu-devel] [PATCH 1/6] cpu: No need to zero-initialize numa_node Eduardo Habkost
2015-03-05 16:13 ` Igor Mammedov
2015-03-05 15:38 ` [Qemu-devel] [PATCH 2/6] cpu: Initialize breakpoint/watchpoint lists on cpu_common_initfn() Eduardo Habkost
2015-03-05 16:15 ` Igor Mammedov
2015-03-05 15:38 ` [Qemu-devel] [PATCH 3/6] cpu: Reorder cpu->as and cpu->thread_id initialization Eduardo Habkost
2015-03-05 16:22 ` Igor Mammedov
2015-03-05 15:38 ` [Qemu-devel] [PATCH 4/6] target-i386: Rename optimize_flags_init() Eduardo Habkost
2015-03-05 16:31 ` Igor Mammedov
2015-03-05 16:38 ` Eduardo Habkost
2015-03-05 15:38 ` [Qemu-devel] [PATCH 5/6] target-i386: Move TCG initialization to realize time Eduardo Habkost
2015-03-05 15:38 ` [Qemu-devel] [PATCH 6/6] target-i386: Call cpu_exec_init() on realize Eduardo Habkost
2015-03-05 16:42 ` Igor Mammedov
2015-03-05 16:44 ` Andreas Färber
2015-03-05 16:48 ` Eduardo Habkost
2015-03-05 16:52 ` [Qemu-devel] [PATCH 0/6] target-i386: Remove side-effects from X86CPU::instance_init 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=1425569930-6660-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=anshul.makkar@profitbricks.com \
--cc=chen.fan.fnst@cn.fujitsu.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=imammedo@redhat.com \
--cc=isimatu.yasuaki@jp.fujitsu.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tangchen@cn.fujitsu.com \
--cc=zhugh.fnst@cn.fujitsu.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).