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] dma_alloc_coherent issue with tg3 in x86_64 build

To: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] dma_alloc_coherent issue with tg3 in x86_64 build
From: Chris Wright <chrisw@xxxxxxxx>
Date: Thu, 28 Jul 2005 14:07:32 -0700
Cc: Chris Wright <chrisw@xxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 28 Jul 2005 21:06:10 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D282822@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D282822@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.6i
* Ian Pratt (m+Ian.Pratt@xxxxxxxxxxxx) wrote:
> > During boot of dom0, I get the following.  Box is remote, so 
> > I'm now waiting for proxy power button pusher ;-)  tg3 init 
> > fails doing dma_alloc_coherent (I assume this is from 
> > tg3_init_one -> tg3_test_dma -> pci_alloc_consistent -> 
> > dma_alloc_coherent).  Looks like an issue with the amount of 
> > memory in dom0.  Is this known?
> Is this with a debug=y build of Xen? I can see how that might provoke
> the situation more than other builds.

Yes, it is.

> Do you know how large a contiguous chunk the tg3 needs? 

I believe that one was just 2 pages.

> I guess we could hold onto a few large chunks before making the dom0
> memory allocation.
> Alternatively, if we get a failure, we should round up to the next power
> of two and then balloon out that much memory. Repeat until success...

I guess that'd be quick that early in boot.


Xen-devel mailing list