From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Roger_Pau_Monn=c3=a9?= Subject: Re: HVMlite ABI specification DRAFT A Date: Fri, 5 Feb 2016 12:50:45 +0100 Message-ID: <56B48C95.1030102@citrix.com> References: <56B38EDE.5090700@citrix.com> <56B396ED.7010209@citrix.com> <56B4757A02000078000CEE45@prv-mh.provo.novell.com> <56B47048.8090206@citrix.com> <56B48A1E02000078000CEF6F@prv-mh.provo.novell.com> <56B487D1.4080902@citrix.com> <56B4995F02000078000CF019@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1aReua-0002nV-P7 for xen-devel@lists.xenproject.org; Fri, 05 Feb 2016 11:50:52 +0000 In-Reply-To: <56B4995F02000078000CF019@prv-mh.provo.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Wei Liu , Stefano Stabellini , Andrew Cooper , Tim Deegan , Paul Durrant , David Vrabel , xen-devel , samuel.thibault@ens-lyon.org, Boris Ostrovsky List-Id: xen-devel@lists.xenproject.org El 5/2/16 a les 12:45, Jan Beulich ha escrit: >>>> On 05.02.16 at 12:30, wrote: >> El 5/2/16 a les 11:40, Jan Beulich ha escrit: >>>>>> On 05.02.16 at 10:50, wrote: >>>> For legacy PCI interrupts, we can parse the MADT inside of Xen in order >>>> to properly setup the lines/overwrites and inject the interrupts that >>>> are not handled by Xen straight into the hardware domain. This will >>>> require us to be able to emulate the same topology as what is found in >>>> native (eg: if there are two IO APICs in the hardware we should also >>>> provide two emulated ones to the hw domain). >>> >>> I don't think MADT contains all the needed information, or else we >>> wouldn't need PHYSDEVOP_setup_gsi. >> >> AFAICT, I think we could do something like: >> >> - IRQs [0, 15]: edge-trigger, low-polarity. >> - IRQs [16, n]: level-triggered, high-polarity. > > That's not a valid assumption - I've seen systems with other settings > on GSI >= 16 ... Then we just propagate how the emulated IO APIC pins are setup to the real one, this should match reality, and is no different from using PHYSDEVOP_setup_gsi. AFAICT it's just a different way of getting the same information. Roger.