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] foreign mapping destructor

To: "Keir Fraser" <Keir.Fraser@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] foreign mapping destructor
From: "King, Steven R" <steven.r.king@xxxxxxxxx>
Date: Fri, 2 Dec 2005 13:25:08 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 02 Dec 2005 21:25:04 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcX3KR4iWxpbkRQzQJCFwGyCpVmgngAXTxGQ
Thread-topic: [Xen-devel] foreign mapping destructor
Thanks Keir, this is helpful -- Just to be definitive: the only
*required* activity in the destructor is to unmap the foreign page from
the domain.  Additional cleanup is use case dependent.

Correct?

-----Original Message-----
From: Keir Fraser [mailto:Keir.Fraser@xxxxxxxxxxxx] 
Sent: Friday, December 02, 2005 2:19 AM
To: King, Steven R
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] foreign mapping destructor


On 2 Dec 2005, at 00:54, King, Steven R wrote:

> The SetPageForeign() macro takes a pointer to a destructor function.
> Can someone please explain the responsibilities of this destructor?
> Thanks for your time,

The 'Foreign' in this context is supposed to refer to a foreign heap. 
That is, the page was not originally allocated from page_alloc.c. So the
destructor is entirely responsible for cleaning up that page of memory
(e.g., in netback.c it unmaps a domU page and sends a packet-transmitted
response to the domU netfront driver). After calling the destructore,
page_alloc.c will not touch that page any more (it will immediately
bail).

  -- Keir

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

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