From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, aliguori@us.ibm.com,
wei.liu2@citrix.com, ehabkost@redhat.com,
stefano.stabellini@eu.citrix.com, sw@weilnetz.de,
mtosatti@redhat.com, agraf@suse.de, blauwirbel@gmail.com,
avi@redhat.com, jan.kiszka@siemens.com,
anthony.perard@citrix.com, pbonzini@redhat.com, afaerber@suse.de
Subject: [Qemu-devel] [PATCH qom-next v2 0/6] target-i386: re-factor CPU creation/initialization to QOM
Date: Wed, 23 May 2012 18:39:35 +0200 [thread overview]
Message-ID: <1337791181-27446-1-git-send-email-imammedo@redhat.com> (raw)
Moving code related to CPU creation and initialization internal parts
from board level into apic and cpu objects will allow X86CPU to better
model QOM object life-cycle.
It will allow to create X86CPU as any other object by creating it with
object_new() then setting properties and then calling x86_cpu_realize()
to make it running. Later x86_cpu_realize() should become realize property.
1 pc: Enable MSI support at APIC level
http://thread.gmane.org/gmane.comp.emulators.kvm.devel/91186
included here to prevent confilict since qom-next doesn't have it
but patches 4, 5 are depending on it. I guess it would be best way to
avoid confilicts, correct me if I'm wrong.
2 target-i386: move cpu halted decision into x86_cpu_reset
3 target-i386: add cpu-model property to x86_cpu
4 pc: move apic_mapped initialization into common apic init code
5 target-i386: make initialize CPU in QOM way
6 target-i386: move reset callback to cpu.c
git tree for testing:
https://github.com/imammedo/qemu/tree/x86-cpu-realize-v2
Compile & Run tested:
target-i386: tcg and kvm mode
i386-linux-user: running of /bin/ls and /usr/bin/make on qemu tree
next reply other threads:[~2012-05-23 16:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 16:39 Igor Mammedov [this message]
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 1/6] pc: Enable MSI support at APIC level Igor Mammedov
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 2/6] target-i386: move cpu halted decision into x86_cpu_reset Igor Mammedov
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 3/6] target-i386: add cpu-model property to x86_cpu Igor Mammedov
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 4/6] pc: move apic_mapped initialization into common apic init code Igor Mammedov
2012-05-23 16:44 ` Peter Maydell
2012-05-23 20:08 ` Jan Kiszka
2012-05-23 21:09 ` Igor Mammedov
2012-05-23 21:26 ` Peter Maydell
2012-05-24 13:10 ` Igor Mammedov
2012-05-24 13:21 ` Peter Maydell
2012-05-24 13:25 ` Jan Kiszka
2012-05-24 13:39 ` Igor Mammedov
2012-05-24 13:45 ` Andreas Färber
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 5/6] target-i386: make initialize CPU in QOM way Igor Mammedov
2012-05-23 21:27 ` Andreas Färber
2012-05-24 9:29 ` Igor Mammedov
2012-05-23 16:39 ` [Qemu-devel] [PATCH qom-next 6/6] target-i386: move reset callback to cpu.c Igor Mammedov
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=1337791181-27446-1-git-send-email-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=anthony.perard@citrix.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=ehabkost@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=sw@weilnetz.de \
--cc=wei.liu2@citrix.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).