This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [PATCH] xen: use the trigger info we already have to cho

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, tom.goetz@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: [PATCH] xen: use the trigger info we already have to choose the irq handler
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Wed, 25 May 2011 10:25:10 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, Thomas Goetz <tcgoetz@xxxxxxxxx>
Delivery-date: Wed, 25 May 2011 07:26:12 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <alpine.DEB.2.00.1105251232020.12963@kaball-desktop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <alpine.DEB.2.00.1105251232020.12963@kaball-desktop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.21 (2010-09-15)
On Wed, May 25, 2011 at 12:33:23PM +0100, Stefano Stabellini wrote:
> Do not use pirq_needs_eoi to decide which irq handler to use because Xen
> always returns true if the guest does not support pirq_eoi_map.
> Use the trigger information we already have from MP-tables and ACPI.
> Signed-off-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
> Reported-by: Thomas Goetz <tcgoetz@xxxxxxxxx>
> Tested-by: Thomas Goetz <tcgoetz@xxxxxxxxx>


Do you prefer those email addresses or tom.goetz@xxxxxxxxxxxxxxxxxxx ?
> -     if (pirq_needs_eoi(irq))
> +     if (shareable)

Ok, so for dom0, the sharable flag is determined by the ACPI parsing.. good.
And for MSI/MSI-X we use xen_bind_pirq_msi_to_irq which sets it to use 

The only hazard which you asked me on IRC is for PV guests with Xen PCI front.
In those cases, we have no idea whether the "GSI" IRQ is edge or level and we
just assume that anything under 16 is edge. Which is 99% right, except if you
are to pass in the ACPI IRQ to the guest, or some other weird creature. The 
part of the PCI front are OK too - they use the xen_bind_pirq_msi_to_irq call.

So, putting on the todo list an extension to the PCI PV protocol to pass 
about the GSI's - whether they are edge or level.

Patch is on the 2.6.40-rc1 train.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>