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] Assigning contiguous memory to a driver domain

To: "Rafal Wojtczuk" <rafal@xxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Assigning contiguous memory to a driver domain
From: "Jan Beulich" <JBeulich@xxxxxxxxxx>
Date: Wed, 15 Sep 2010 10:50:49 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 15 Sep 2010 02:52:38 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100915093910.GC1583@email>
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: <20100914092439.GA1000@email> <4C8F5E580200007800015F71@xxxxxxxxxxxxxxxxxx> <20100915090842.GB1583@email> <20100915093910.GC1583@email>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
>>> On 15.09.10 at 11:39, Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> On Wed, Sep 15, 2010 at 11:08:42AM +0200, Rafal Wojtczuk wrote:
>> On Tue, Sep 14, 2010 at 10:36:56AM +0100, Jan Beulich wrote:
>> > >>> On 14.09.10 at 11:24, Rafal Wojtczuk <rafal@xxxxxxxxxxxxxxxxxxxxxx> 
>> > >>> wrote:
>> > > Hello,
>> > > 
>> > > Could someone guide me in the right direction with the topic of assigning
>> > > contiguous memory to a domain.
>> > > 
>> > > I have an issue with a PV domain that is assigned a PCI device. 
>> > > Sometimes, 
> 
>> > > the 
>> > > driver fails to load
>> > > Sep 13 10:36:43 localhost kernel: [  103.651858] iwlagn 0000:00:01.0:
>> > > firmware: requesting iwlwifi-4965-2.ucode
>> > > Sep 13 10:36:43 localhost kernel: [  103.669105] iwlagn 0000:00:01.0: 
> loaded
>> > > firmware version 228.61.2.24
>> > > Sep 13 10:36:43 localhost kernel: [  103.669263] iwlagn 0000:00:01.0: 
> failed
>> > > to allocate pci memory
>> > > 
>> > > The reason seems to be that the domain does not have enough contiguous
>> > > memory, in mfn terms.
>> > 
>> > No, how (dis)contiguous the memory of a domain is doesn't matter
>> > here. What matters is whether the domain can *make* the requested
>> > memory contiguous, and that depends on how much contiguous
>> > memory Xen has at the point of the allocation.
>> 
>> Ah, so you are saying that regardless of whether a domain has some
>> contiguous memory, the driver will call xen_create_contiguous_region when 
> allocating
>> memory (via dma_alloc_coherent ?).
>> 
>> Slightly out-of-the-list-scope: is there a convention when a driver should
>> allocate DMA-able memory ? Is it safe to assume that as soon as the driver
>> has loaded, it will no longer need to call xen_create_contiguous_region
>> anymore and we can use up all free Xen memory ? 
> 
> Hmm, at least in case of tg3 driver, if xen free memory = 0, after I have
> done "ifconfig eth0 down" in the driver domain, the subsequent "ifconfig 
> eth0 up" 
> failed with "SIOCSIFFLAGS: Cannot allocate memory".

Sure - why would the driver waste resources when the device may
not be used.

> So, it looks like in order to make a PV driver domain work, there must be 
> some Xen free memory 
> all the time ?

Potentially yes, but this really depends on how the respective
driver is written.

> Moreover, this free Xen memory must be contiguous to some
> extent; is there any way to assure this ?

No.

Jan


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