WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH PV_OPS PCIFRONT]

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [PATCH PV_OPS PCIFRONT]
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Fri, 6 Nov 2009 16:50:35 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 06 Nov 2009 13:53:29 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4AF497BE.1030806@xxxxxxxx>
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: <1257456819-782-1-git-send-email-konrad.wilk@xxxxxxxxxx> <20091105220414.GA3820@xxxxxxxxxxxxxxxxxxx> <4AF497BE.1030806@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Fri, Nov 06, 2009 at 01:40:14PM -0800, Jeremy Fitzhardinge wrote:
> On 11/05/09 14:04, Konrad Rzeszutek Wilk wrote:
> >> That is it for right now. The driver works with INTx and MSI cards. I've 
> >> tested
> >> with USB and network (Broadcom) succesfully. There is still some more work 
> >> to do:
> >>  - MSI disable is not yet in,
> >>  - no MSI-X enable/disable functionality.
> >>     
> > and:
> >  - If 4GB or more are allocated to the domain, you get this:
> >
> > PCI: Warning: Cannot find a gap in the 32bit address range
> > PCI: Unassigned devices with 32bit resource registers may break!
> >
> >    and the device shows up as disabled and is not usuable.
> >   
> 
> Presumably less than 4G can trigger this.  My rough thought about this
> was to always reserve a chunk of memory under 4G to make space for this
> kind of thing, and push the displaced memory higher.

<nods> This would be done in the xc_build_domain_linux_something ?

> >
> > WARNING: at drivers/pci/msi.c:602 pci_enable_msi_block+0xcd/0x339()
> > .. snip ..
> > Call Trace:
> >  [<ffffffff8107ed59>] warn_slowpath_common+0xc9/0x10c
> >  [<ffffffff8107edcc>] warn_slowpath_null+0x30/0x4d
> >  [<ffffffff81362cec>] pci_enable_msi_block+0xcd/0x339
> >  [<ffffffff814006ec>] ? pciback_do_op+0x0/0x1b4
> >  [<ffffffff8140469e>] pciback_enable_msi+0x3e/0xb0
> >  [<ffffffff814007b9>] pciback_do_op+0xcd/0x1b4
> > ..snip..
> >   
> 
> What does that warning mean?

Something about slowpath. Didn't dive any deeper in this. I think it complains
about the workqueue taking too long to do its job.
> 
> > But besides that it works :-)
> >   
> 
> Good!  I'll throw it into the mix and see how it flies.

<crosses his fingers>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel