From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jeremy Fitzhardinge <jeremy@goop.org>
Subject: Re: Re: APIC rework
Date: Mon, 16 Nov 2009 21:20:05 -0800
Message-ID: <4B023285.50702@goop.org>
References: <C727CCCB.C018%keir.fraser@eu.citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <C727CCCB.C018%keir.fraser@eu.citrix.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: Xen-devel <xen-devel@lists.xensource.com>, "Han,
	Weidong" <weidong.han@intel.com>, "Zhang,
	Xiantao" <xiantao.zhang@intel.com>, Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
List-Id: xen-devel@lists.xenproject.org

On 11/16/09 19:45, Keir Fraser wrote:
> It's kind of a shame to need this though. Is there no way for the hypervisor
> to work out automatically whether an older dom0 is running? Or work out the
> trigger/level stuff for itself (after all it parses the relevant bios tables
> just like dom0)?

If Xen can set the interrupt triggering by itself, why would it ever
need dom0 to do it?  Couldn't it just preconfigure all the pins, and
then wait for dom0 to provide/request the pirq<->evtchn mapping?

    J