From mboxrd@z Thu Jan 1 00:00:00 1970 From: felipe.balbi@linux.intel.com (Felipe Balbi) Date: Thu, 08 Sep 2016 15:07:04 +0300 Subject: [PATCH V6 0/3] Integration of function trace with System Trace IP blocks In-Reply-To: <1473303784-18262-1-git-send-email-zhang.chunyan@linaro.org> References: <1473303784-18262-1-git-send-email-zhang.chunyan@linaro.org> Message-ID: <87inu6h9xz.fsf@linux.intel.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, Chunyan Zhang writes: > IP blocks allowing a variety of trace sources to log debugging > information to a pre-defined area have been introduced on a couple of > architecture [1][2]. These system trace blocks (also known as STM) > typically follow the MIPI STPv2 protocol [3] and provide a system wide > logging facility to any device, running a kernel or not, with access > to the block's log entry port(s). Since each trace message has a > timestamp, it is possible to correlate events happening in the entire > system rather than being confined to the logging facility of a single > entity. > > This patchset is trying to use STM IP blocks to store function tracing > information produced by Ftrace and I'm taking the Function trace > (trace type is TRACE_FN) as the example in this patchset, but other > types of traces also can be supported. > > Logging information generated by the Ftrace subsystem to STM and gathered > in the sink device can be used in conjunction with trace data from other > board components, also collected in the same trace sink. > > This example is using ARM coresight STM but the same would apply to any > other architecture wishing to do the same. > > Comments would be greatly appreciated. showing up late to the bandwagon, but this is very good. I've been toying with the idea of exporting ftrace via USB and this will help quite a bit. Thanks :-) I'll add to my TODO a look at this series. Great work. -- balbi -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 800 bytes Desc: not available URL: From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965609AbcIHMHu (ORCPT ); Thu, 8 Sep 2016 08:07:50 -0400 Received: from mga09.intel.com ([134.134.136.24]:2040 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S964861AbcIHMHr (ORCPT ); Thu, 8 Sep 2016 08:07:47 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,300,1470726000"; d="asc'?scan'208";a="1037019417" From: Felipe Balbi To: Chunyan Zhang , rostedt@goodmis.org, mathieu.poirier@linaro.org, alexander.shishkin@linux.intel.com, mingo@redhat.com Cc: arnd@arndb.de, mike.leach@arm.com, tor@ti.com, philippe.langlais@st.com, nicolas.guion@st.com, zhang.lyra@gmail.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH V6 0/3] Integration of function trace with System Trace IP blocks In-Reply-To: <1473303784-18262-1-git-send-email-zhang.chunyan@linaro.org> References: <1473303784-18262-1-git-send-email-zhang.chunyan@linaro.org> User-Agent: Notmuch/0.22.1+63~g994277e (https://notmuchmail.org) Emacs/25.1.3 (x86_64-pc-linux-gnu) Date: Thu, 08 Sep 2016 15:07:04 +0300 Message-ID: <87inu6h9xz.fsf@linux.intel.com> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi, Chunyan Zhang writes: > IP blocks allowing a variety of trace sources to log debugging > information to a pre-defined area have been introduced on a couple of > architecture [1][2]. These system trace blocks (also known as STM) > typically follow the MIPI STPv2 protocol [3] and provide a system wide > logging facility to any device, running a kernel or not, with access > to the block's log entry port(s). Since each trace message has a > timestamp, it is possible to correlate events happening in the entire > system rather than being confined to the logging facility of a single > entity. > > This patchset is trying to use STM IP blocks to store function tracing > information produced by Ftrace and I'm taking the Function trace > (trace type is TRACE_FN) as the example in this patchset, but other > types of traces also can be supported. > > Logging information generated by the Ftrace subsystem to STM and gathered > in the sink device can be used in conjunction with trace data from other > board components, also collected in the same trace sink.=20=20 > > This example is using ARM coresight STM but the same would apply to any > other architecture wishing to do the same. > > Comments would be greatly appreciated. showing up late to the bandwagon, but this is very good. I've been toying with the idea of exporting ftrace via USB and this will help quite a bit. Thanks :-) I'll add to my TODO a look at this series. Great work. =2D-=20 balbi --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJX0VRoAAoJEMy+uJnhGpkGyasP+wSe6QLIxeWpmz+IOiURvQcQ JhhlBOXdvWqrYLK7BdqXJecCXR5fbp7HWU/2DjuD8c4w/fKhfFj0XQjrwyBTeUBd 6DGSIohMiLMYEs4sycL4hlsuipPXZFIn7FGgWyISmj9Qbuo9dF8Ax4qxPXHPXJPy nzVuX8GT03TPitezTmRnZZfKBhQJcknVQhV3QUdpqfA/h02+oLpdzWjSb+Kbn+Nj ZC4DOBP8CGk7+hHs8DgJCBPFAJPH8QBMBbcOIvwXnVoEy1icAI/fmtlJJKijTJ/c FgbPBWypeyaPqnqCaqurfgS+35CLrnh3gugc+gyYmWrbAuflmRyR7sjvwHmKuITr uM/7E/ctH7paUuQhj2LQcWYeTkEit81XesEml6oTVi1geqld69p/Jlj76nVkgup1 /6ADdnDVq0jxXfNJ17QdpI1+New34oa9j+sbjpiXASMt92c43yRa1kvQ9z3k9wkd fFlNcyLSfGcWnEKk6oBQVIzHJBnyflcLFCNPUuGKrsczWhi1HwV0M81wwJT+iRMJ uHITUk1Op/c6+KQlyR25YsX9cPk2p5dCWQ/4HWGNrDRPTybgc+AtDhuwAKF254a5 8vmScsDPEHntHqqIDQIeNySu/ohPuLG+jqxUk0T97jiBRi5QWOo/uY6tUDM3Nd6l TADPvu7UzcJkUNWVfom+ =CZEK -----END PGP SIGNATURE----- --=-=-=--