From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:55088) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TaXR3-0001at-0M for qemu-devel@nongnu.org; Mon, 19 Nov 2012 14:55:16 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TaXQy-0004Ty-9u for qemu-devel@nongnu.org; Mon, 19 Nov 2012 14:55:12 -0500 Message-ID: <1353354860.23412.93.camel@pasglop> From: Benjamin Herrenschmidt Date: Tue, 20 Nov 2012 06:54:20 +1100 In-Reply-To: References: <1352774820-22804-1-git-send-email-david@gibson.dropbear.id.au> <1352774820-22804-4-git-send-email-david@gibson.dropbear.id.au> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Mime-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH 03/12] pseries: Move XICS initialization before cpu initialization List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Michael Ellerman , qemu-ppc@nongnu.org, qemu-devel@nongnu.org, David Gibson On Mon, 2012-11-19 at 17:22 +0100, Alexander Graf wrote: > > Currently, the pseries machine initializes the cpus, then the XICS > > interrupt controller. However, to support the upcoming in-kernel XICS > > implementation we will need to initialize the irq controller before the > > vcpus. This patch makes the necesssary rearrangement. This means the > > xics init code can no longer auto-detect the number of cpus ("interrupt > > servers" in XICS terminology) and so we must pass that in explicitly from > > the platform code. > > Does this still hold true with the new in-kernel interrupt controller workflow? We need to look into this. The in-kernel ICPs will still certainly be created early along with the VCPUs, however we might be able to delay the creation of the qemu emulation when not using the former. Cheers, Ben.