From mboxrd@z Thu Jan 1 00:00:00 1970 From: stefanha@redhat.com (Stefan Hajnoczi) Date: Tue, 23 Aug 2016 11:54:30 -0400 Subject: [lttng-dev] [Qemu-devel] [PATCH 0/6] hypertrace: Lightweight guest-to-QEMU trace channel In-Reply-To: <8737lypajh.fsf@fimbulvetr.bsc.es> References: <147041636348.2523.2954972609232949598.stgit@fimbulvetr.bsc.es> <20160818105424.GD4850@stefanha-x1.localdomain> <8737lypajh.fsf@fimbulvetr.bsc.es> Message-ID: <20160823155430.GB3948@stefanha-x1.localdomain> On Sun, Aug 21, 2016 at 02:32:34PM +0200, Lluís Vilanova wrote: > Unfortuntely, I've been unable to to make dtrace recognise QEMU's events (I'm > only able to see the host kernel events). If someone with more experience on it > can help me use dtrace with QEMU's events, I'll also add the supporting library > to let dtrace do the callout to QEMU's moitor interface and control the events, > and add a prperly useful example of that on the hypertrace docs (which was my > original intention). Which "dtrace" and host OS are you using? QEMU builds with static user-space probes. You need to tell DTrace or SystemTap to enable those probes in order to record trace data. Stefan -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: