From: Glauber Costa <glommer@redhat.com>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com
Subject: [Qemu-devel] [PATCH 0/4] Simplify cpu initialization
Date: Wed, 6 May 2009 10:49:38 -0400 [thread overview]
Message-ID: <1241621382-21577-1-git-send-email-glommer@redhat.com> (raw)
Currently, there are pieces of cpu initialization being done in two
different places. The big part of it, is done inside cpu_x86_init,
while minor others are done in pc.c, after cpu_x86_init returns.
For things like halting cpus != 0, registering reset handler, etc,
there is no reason whatsoever for not doing it in cpu initialization.
The apic initialization should be moved there too, and theorectically,
it should not depend on pci machine. However, it currently breaks
our isa machine, and to avoid a hack, it is left where it is.
next reply other threads:[~2009-05-06 14:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 14:49 Glauber Costa [this message]
2009-05-06 14:49 ` [Qemu-devel] [PATCH 1/4] move registering of cpu_reset to inside cpu_init Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 2/4] move CPUID_APIC flag to where it belongs Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 3/4] move halted state setting to inside of cpu_x86_init Glauber Costa
2009-05-06 14:49 ` [Qemu-devel] [PATCH 4/4] move apic functions to a separate apic.h header Glauber Costa
2009-05-06 15:52 ` [Qemu-devel] " Jan Kiszka
2009-05-06 16:08 ` Glauber Costa
2009-05-06 15:45 ` [Qemu-devel] Re: [PATCH 3/4] move halted state setting to inside of cpu_x86_init Jan Kiszka
2009-05-06 19:31 ` [Qemu-devel] " Blue Swirl
2009-05-06 21:42 ` Glauber Costa
2009-05-06 15:40 ` [Qemu-devel] Re: [PATCH 2/4] move CPUID_APIC flag to where it belongs Jan Kiszka
2009-05-06 15:51 ` Glauber Costa
2009-05-06 17:29 ` Stanislav
2009-05-06 17:41 ` Glauber Costa
2009-05-06 17:43 ` Stanislav
2009-05-06 18:17 ` Anthony Liguori
2009-05-06 17:02 ` [Qemu-devel] Re: [PATCH 1/4] move registering of cpu_reset to inside cpu_init Jan Kiszka
2009-05-06 19:36 ` [Qemu-devel] " Blue Swirl
2009-05-06 21:45 ` Glauber Costa
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=1241621382-21577-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=aliguori@us.ibm.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).