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


Re: [Xen-devel] Re: [GIT PATCH v2 0/14] xen: events: cleanups + ween off

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [GIT PATCH v2 0/14] xen: events: cleanups + ween off nr_irqs
From: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
Date: Fri, 11 Mar 2011 09:17:00 +0000
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "linux-kernel@xxxxxxxxxxxxxxx" <linux-kernel@xxxxxxxxxxxxxxx>, Stefano Stabellini <Stefano.Stabellini@xxxxxxxxxxxxx>
Delivery-date: Fri, 11 Mar 2011 01:17:31 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20110311003841.GA3063@xxxxxxxxxxxx>
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>
Organization: Citrix Systems, Inc.
References: <1299773279.17339.813.camel@xxxxxxxxxxxxxxxxxxxxxx> <20110310225726.GA2983@xxxxxxxxxxxx> <20110311003841.GA3063@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Fri, 2011-03-11 at 00:38 +0000, Konrad Rzeszutek Wilk wrote:
> > I am having difficulties with passthrough of an USB device. Somehow the
> > irq count is not going up at all (both in dom0 and domU) and it looks to
> > be doing just simple polling. I've rebased the xen-pciback to be on top
> > of your changes and apply cleanly. The whole lot is now in #master
> I think your patchset breaks the 'xc_physdev_map_pirq' call. Looks like
> libxl_pci.c reads from /sys/bus/pci/devices/<BDF>/irq to figure out what value
> to pass. With these patches we wouldn't neccessarily pass in the right
> PIRQ value. Any ideas?

I'll have to have a think. At best there's some confusing usage of the
term pirq in there. (which is not unexpected, various subsystems use it
for different things.)

Certainly I would never expect to read a Xen pirq out of /sys/.../irq
and that appears to be how this value is being used...


Xen-devel mailing list

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