From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [RFC 0/5] Tracing backends Date: Sun, 23 May 2010 17:48:10 +0200 Message-ID: <4BF94E3A.7010603@web.de> References: <1274562503-10713-1-git-send-email-stefanha@linux.vnet.ibm.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig654477F0A54F0570EF9683D0" Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org, Prerna Saxena , Anthony Liguori To: Stefan Hajnoczi Return-path: Received: from fmmailgate03.web.de ([217.72.192.234]:34546 "EHLO fmmailgate03.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752686Ab0EWPsM (ORCPT ); Sun, 23 May 2010 11:48:12 -0400 In-Reply-To: <1274562503-10713-1-git-send-email-stefanha@linux.vnet.ibm.com> Sender: kvm-owner@vger.kernel.org List-ID: This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig654477F0A54F0570EF9683D0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: quoted-printable Stefan Hajnoczi wrote: > The following patches against qemu.git allow static trace events to be = declared > in QEMU. Trace events use a lightweight syntax and are independent of = the > backend tracing system (e.g. LTTng UST). >=20 > Supported backends are: > * my trivial tracer ("simple") > * LTTng Userspace Tracer ("ust") > * no tracer ("nop", the default) >=20 > The ./configure option to choose a backend is --trace-backend=3D. >=20 > Main point of this patchset: adding new trace events is easy and we can= switch > between backends without modifying the code. >=20 > Prerna: Would you like to add your tracing system as a backend? This w= ould be > similar to my patches to add "simple" and "ust" backend support. >=20 > Jan: Adding kernel marker backend support should be straightforward if = you are > interested. >=20 > These patches are also available at: > http://repo.or.cz/w/qemu/stefanha.git/shortlog/refs/heads/tracing >=20 Nice! Will have a closer look once timer permits, specifically to check how ftrace can be added to this. Looks indeed straightforward on first sight. Jan --------------enig654477F0A54F0570EF9683D0 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkv5TjoACgkQitSsb3rl5xTcHQCg745fquylnxR0IS/RToJYxrPP u5sAmQFUBRkMYxsmlRl7Fb85Xd8dO/BD =mnnJ -----END PGP SIGNATURE----- --------------enig654477F0A54F0570EF9683D0--