From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:50945)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@redhat.com>) id 1WAKjJ-0006Fh-KR
	for qemu-devel@nongnu.org; Mon, 03 Feb 2014 09:42:39 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <stefanha@redhat.com>) id 1WAKjD-00030b-La
	for qemu-devel@nongnu.org; Mon, 03 Feb 2014 09:42:33 -0500
Received: from mx1.redhat.com ([209.132.183.28]:42064)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <stefanha@redhat.com>) id 1WAKjD-00030T-Dg
	for qemu-devel@nongnu.org; Mon, 03 Feb 2014 09:42:27 -0500
Date: Mon, 3 Feb 2014 15:40:01 +0100
From: Stefan Hajnoczi <stefanha@redhat.com>
Message-ID: <20140203144001.GA12840@stefanha-thinkpad.redhat.com>
References: <20140131160902.32741.2680.stgit@fimbulvetr.bsc.es>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <20140131160902.32741.2680.stgit@fimbulvetr.bsc.es>
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Qemu-devel] [PATCH 00/12] trace: [tcg] Allow tracing guest
 events in TCG-generated code
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: =?iso-8859-1?Q?Llu=EDs?= Vilanova <vilanova@ac.upc.edu>
Cc: Stefan Weil <weil@mail.berlios.de>, Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org, Aurelien Jarno <aurelien@aurel32.net>, Richard Henderson <rth@twiddle.net>

On Fri, Jan 31, 2014 at 05:09:03PM +0100, Llu=EDs Vilanova wrote:
> Adds the base ability to specify which events in the "trace-events" fil=
e may be
> used to trace guest activity in the TCG code (using the "tcg" event pro=
pery).
>=20
> Such events generate an extra set of tracing functions that can be call=
ed during
> TCG code generation and will automatically redirect a call to the appro=
priate
> backend-dependent tracing functions when the guest code is executed.

I've never worked on TCG but this seems like a good idea: a way to plant
trace events in TCG-generated code.

CCing TCG folks to check they are happy with the approach

Once any high-level discussion is done I'll review the tracing changes.

Stefan