From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: [PATCH] Make the hypercall PHYSDEVOP_alloc_irq_vector hypercall dummy. Date: Thu, 03 Sep 2009 13:59:57 -0700 Message-ID: <4AA02E4D.9080005@goop.org> References: <706158FABBBA044BAD4FE898A02E4BC201C435171B@pdsmsx503.ccr.corp.intel.com> <4A9EE7B0.7080705@goop.org> <706158FABBBA044BAD4FE898A02E4BC201C43C4FB1@pdsmsx503.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <706158FABBBA044BAD4FE898A02E4BC201C43C4FB1@pdsmsx503.ccr.corp.intel.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Zhang, Xiantao" Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 09/03/09 06:14, Zhang, Xiantao wrote: > IMO, dom0 should only cares about pirq(==GSI) and doesn't need to know the ifno about vector and specific apic&pin at all. Since Xen also knows GSI info, so dom0 and Xen can build irq mapping(xen's irq and dom0's pirq) through it. Yes, but if dom0 rebinds the pirq<->gsi association, will Xen maintain its internal structures correctly? > Maybe we can get rid of ioapic in dom0 eventually. > Yes, I think so (see other mail). J