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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] LTTng-Xen Buffer shared between the hypervisor and a dom0 process
From: Mathieu Desnoyers <compudj@xxxxxxxxxxxxxxxxxx>
Date: Thu, 8 Mar 2007 04:26:27 -0500
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 08 Mar 2007 01:25:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C215710B.37F0%Keir.Fraser@xxxxxxxxxxxx>
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: <20070307192448.GA23656@Krystal> <C215710B.37F0%Keir.Fraser@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
* Keir Fraser (Keir.Fraser@xxxxxxxxxxxx) wrote:
> 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.
> 

Not exactly : when xen wants to end writing to its buffers, it disables
writing, does a subbuffer switch and sets the buffer "finalize" flag to
1.  It then sends a VIRQ to lttd-xen. lttd-xen reads the last subbuffers
(using a get_cpu/put_cpu and get_facilities/put_facilities cmd of the
ltt hypercall to select the offset to read and then reads the buffers)
and is then ready to release the buffers. At that specific point, I
would like all the trace information (xmalloc'd and xenheap shared) to
be freed. But I would also like it to be freed if lttd is killed (so
when file descriptors and memory maps are freed).

Mathieu

>  -- 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 ?
> 
> 

-- 
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68

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