|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] LTTng Xen port
To: |
xen-devel@xxxxxxxxxxxxxxxxxxx |
Subject: |
Re: [Xen-devel] LTTng Xen port |
From: |
Mark Williamson <mark.williamson@xxxxxxxxxxxx> |
Date: |
Fri, 15 Dec 2006 05:02:05 +0000 |
Cc: |
Jimi Xenidis <jimix@xxxxxxxxxxxxxx>, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>, Robert Wisniewski <bob@xxxxxxxxxxxxxx>, Tony Breeds <tony@xxxxxxxxxxxxxxxxxx>, michel.dagenais@xxxxxxxxxx, Mathieu Desnoyers <compudj@xxxxxxxxxxxxxxxxxx>, Rob Gardner <rob.gardner@xxxxxx> |
Delivery-date: |
Thu, 14 Dec 2006 21:02:16 -0800 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20061213022557.GT27551@xxxxxxxxxxxxxxxxxx> |
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: |
<20061212172923.GA24883@Krystal> <20061212221401.GA18277@Krystal> <20061213022557.GT27551@xxxxxxxxxxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
KMail/1.9.5 |
> I suspect that xenbaked uses it,
> http://lxr.xensource.com/lxr/source/tools/xenmon/xenbaked.c
> ---
> 262 int eventchn_init(void)
> 263 {
> 264 int rc;
> 265
> 266 // to revert to old way:
> 267 if (0)
> 268 return -1;
> 269
> 270 xce_handle = xc_evtchn_open();
> 271
> 272 if (xce_handle < 0)
> 273 perror("Failed to open evtchn device");
> 274
> 275 if ((rc = xc_evtchn_bind_virq(xce_handle, VIRQ_TBUF)) == -1)
> 276 perror("Failed to bind to domain exception virq port");
> 277 virq_port = rc;
> 278
> 279 return xce_handle;
> 280 }
> ---
>
> With appropriate triggering, in xen/common/trace.c
Ah yes.
It should be fairly trivial to copy this code into xentrace.c and then replace
the nanosleep with a wait on that event. This would probably be worthwhile
as an interim solution until we figure out what next gen tracing ought to
look like.
Cheers,
Mark
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
|
|
|
|