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] Re: PCI passthrough stopped working, brainache!

To: Andy Burns <xen.lists@xxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: PCI passthrough stopped working, brainache!
From: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
Date: Sat, 15 Oct 2011 13:15:26 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Sat, 15 Oct 2011 05:16:28 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <CAE1-PRf8ySeBVYFqxoc6Wd_K4fK=UCLYx+sOzDgNwUU5XhiR2Q@xxxxxxxxxxxxxx>
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: <CAE1-PReH55X375oSb_gx4K_2iTTo67xpFfS8r7zv3KPtiOxj_A@xxxxxxxxxxxxxx> <CAE1-PRc9LqO07TjH3TnfSnEB8gLkBhw2211syeA04XPWts62Xg@xxxxxxxxxxxxxx> <CAE1-PRfg3fkMMSQyPO+y8dqxcE-KNJc--6bx84aouaQorOF27w@xxxxxxxxxxxxxx> <20111012035032.GB26092@xxxxxxxxxxxxxxxxx> <CAE1-PRfuo10T2iKJUNoY=Aj4S_TjUbiPT1jARv+iD7g+1qWuNg@xxxxxxxxxxxxxx> <CAE1-PRd9Kicm=dRtDmPKGXM8-fp62NyvDdpww38jA3Afwrt8+g@xxxxxxxxxxxxxx> <20111013181543.GF15499@xxxxxxxxxxxxxxxxx> <CAE1-PRfGTxeQ59jmHfB6bKKk2+B5bNnKhAvXoV-5P__+nkhgKQ@xxxxxxxxxxxxxx> <1318674976.11016.24.camel@xxxxxxxxxxxxxxxxxxxx> <CAE1-PRf8ySeBVYFqxoc6Wd_K4fK=UCLYx+sOzDgNwUU5XhiR2Q@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Sat, 2011-10-15 at 11:54 +0100, Andy Burns wrote:
> On 15 October 2011 11:36, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
> 
> > In general if a driver is correctly using the DMA API things should
> > never be within the swiotlb.
> 
> OK, they just looked coincidentally similar.
> 
> > I think you've got 8G of RAM so one thing which might be worth trying is
> > to give "mem=2G" (or perhaps 3G) on the hypervisor command line.
> 
> Yes I do have 8GB, will give it a try.
> 
> > I wonder if the hypervisor's "dma_bits" option has any relevance here?
> > Might be worth a go?
> 
> I noticed that parameter, but couldn't see much indication of sensible
> values, something a few bits less than 32 perhaps?

Anything <32 would be a good guess, maybe try 30? Even 32 might be
worthwhile to try (not sure what you are getting by default).

Ian.

> > In general I think these sorts cards use I2C extensively, i.e. the tuner
> > etc is on an i2c bus, so I wouldn't expect anything to work at all
> > without it.
> 
> Yes, that part of the card is working, w_scan can control the tuner
> and detect when it latches onto valid muxes, receiving the bulk
> datastream from the demodulator is the problem.



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