From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M1iRU-0005Gu-1a
	for qemu-devel@nongnu.org; Wed, 06 May 2009 10:49:52 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M1iRP-0005Er-2s
	for qemu-devel@nongnu.org; Wed, 06 May 2009 10:49:51 -0400
Received: from [199.232.76.173] (port=60947 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M1iRO-0005Ei-HN
	for qemu-devel@nongnu.org; Wed, 06 May 2009 10:49:46 -0400
Received: from mx2.redhat.com ([66.187.237.31]:38804)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <glommer@redhat.com>) id 1M1iRN-0000YV-NP
	for qemu-devel@nongnu.org; Wed, 06 May 2009 10:49:45 -0400
From: Glauber Costa <glommer@redhat.com>
Date: Wed,  6 May 2009 10:49:38 -0400
Message-Id: <1241621382-21577-1-git-send-email-glommer@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] Simplify cpu initialization
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: qemu-devel@nongnu.org
Cc: aliguori@us.ibm.com

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.