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] LTTng-Xen Buffer shared between the hypervisor and a dom

To: Mathieu Desnoyers <compudj@xxxxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] LTTng-Xen Buffer shared between the hypervisor and a dom0 process
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 08 Mar 2007 07:51:39 +0000
Delivery-date: Wed, 07 Mar 2007 23:50:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <20070307192448.GA23656@Krystal>
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: AcdhVpp42MJ4os1JEduPKQAWy6hiGQ==
Thread-topic: [Xen-devel] LTTng-Xen Buffer shared between the hypervisor and a dom0 process
User-agent: Microsoft-Entourage/11.3.3.061214
On 7/3/07 19:24, "Mathieu Desnoyers" <compudj@xxxxxxxxxxxxxxxxxx> wrote:

> Then, I would like to release some kind of reference count of this
> mapping from the hypervisor. I do the following which results in page
> faults (probably because it tries to free memory still accessed by
> lttd-xen) :

What's the shutdown order you're looking for? It sounds like you want Xen to
tell lttd-xen when it should quit, which seems to me the wrong way round.

 -- Keir

>             free_xenheap_pages(
>                 rawbuf,
>                 get_order_from_bytes(chan->alloc_size * num_possible_cpus()));
> 
> 
> And then, when we are sure that no more data can be written in the
> buffer, lttd-xen is ready to exit. It unmaps the buffer just before exit :
> 
>             err_ret = munmap(pair->mmap, pair->subbuf_size * pair->n_subbufs);
> 
> Do you know any proper way to achieve what I am looking for ?



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