linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <arnaldo.melo@gmail.com>
Cc: Jiri Olsa <jolsa@redhat.com>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <peterz@infradead.org>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>
Subject: Re: [PATCH 01/11] perf intel-pt: Add new packets for PEBS via PT
Date: Thu, 13 Jun 2019 11:13:54 +0300	[thread overview]
Message-ID: <f94716f2-5696-ad3b-64d7-0620975116e2@intel.com> (raw)
In-Reply-To: <20190612132852.GB4836@kernel.org>

On 12/06/19 4:28 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Jun 12, 2019 at 03:52:11PM +0300, Adrian Hunter escreveu:
>> On 12/06/19 3:41 PM, Arnaldo Carvalho de Melo wrote:
>>> Em Wed, Jun 12, 2019 at 08:58:00AM +0300, Adrian Hunter escreveu:
>>>> On 12/06/19 3:09 AM, Arnaldo Carvalho de Melo wrote:
>>>>> Em Mon, Jun 10, 2019 at 10:27:53AM +0300, Adrian Hunter escreveu:
>>>>>> Add 3 new packets to supports PEBS via PT, namely Block Begin Packet (BBP),
>>>>>> Block Item Packet (BIP) and Block End Packet (BEP). PEBS data is encoded
>>>>>> into multiple BIP packets that come between BBP and BEP. The BEP packet
>>>>>> might be associated with a FUP packet. That is indicated by using a
>>>>>> separate packet type (INTEL_PT_BEP_IP) similar to other packets types with
>>>>>> the _IP suffix.
>>>>>>
>>>>>> Refer to the Intel SDM for more information about PEBS via PT.
>>>>>
>>>>> In these cases would be nice to provide an URL and page number, for
>>>>> convenience.
>>>>
>>>> Intel SDM:
>>>>
>>>> 	https://software.intel.com/en-us/articles/intel-sdm
>>>>
>>>> May 2019 version: Vol. 3B 18.5.5.2 PEBS output to Intel® Processor Trace
>>>
>>> Thanks! I'll add to that cset.
>>>
>>> What about the kernel bits?
>>
>> Awaiting V2, here is a link to the patches:
>>
>> 	https://lore.kernel.org/lkml/20190502105022.15534-1-alexander.shishkin@linux.intel.com/
> 
> yeah, I saw those and PeterZ's comments, that is why I asked about them
> :-)
>  
>> There is also still a few more tools changes dependent upon the kernel patches.
> 
> But I think I can go ahead and push the decoder bits, when the kernel
> patches get merged we'll be almost ready to make full use of what it
> provides, right?

Yes



  reply	other threads:[~2019-06-13 16:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-10  7:27 [PATCH 00/11] perf intel-pt: Prepare for PEBS via PT Adrian Hunter
2019-06-10  7:27 ` [PATCH 01/11] perf intel-pt: Add new packets " Adrian Hunter
2019-06-12  0:09   ` Arnaldo Carvalho de Melo
2019-06-12  5:58     ` Adrian Hunter
2019-06-12 12:41       ` Arnaldo Carvalho de Melo
2019-06-12 12:52         ` Adrian Hunter
2019-06-12 13:28           ` Arnaldo Carvalho de Melo
2019-06-13  8:13             ` Adrian Hunter [this message]
2019-07-04 16:10             ` Alexander Shishkin
2019-06-22  6:35   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 02/11] perf intel-pt: Add Intel PT packet decoder test Adrian Hunter
2019-06-22  6:36   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 03/11] perf intel-pt: Add decoder support for PEBS via PT Adrian Hunter
2019-06-22  6:37   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 04/11] perf intel-pt: Prepare to synthesize PEBS samples Adrian Hunter
2019-06-22  6:38   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 05/11] perf intel-pt: Factor out common sample preparation for re-use Adrian Hunter
2019-06-22  6:38   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 06/11] perf intel-pt: Synthesize PEBS sample basic information Adrian Hunter
2019-06-22  6:39   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:27 ` [PATCH 07/11] perf intel-pt: Add gp registers to synthesized PEBS sample Adrian Hunter
2019-06-22  6:40   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:28 ` [PATCH 08/11] perf intel-pt: Add xmm " Adrian Hunter
2019-06-22  6:40   ` [tip:perf/core] perf intel-pt: Add XMM " tip-bot for Adrian Hunter
2019-06-10  7:28 ` [PATCH 09/11] perf intel-pt: Add lbr information " Adrian Hunter
2019-06-22  6:41   ` [tip:perf/core] perf intel-pt: Add LBR " tip-bot for Adrian Hunter
2019-06-10  7:28 ` [PATCH 10/11] perf intel-pt: Add memory " Adrian Hunter
2019-06-22  6:42   ` [tip:perf/core] " tip-bot for Adrian Hunter
2019-06-10  7:28 ` [PATCH 11/11] perf intel-pt: Add callchain " Adrian Hunter
2019-06-22  6:43   ` [tip:perf/core] " tip-bot for Adrian Hunter

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f94716f2-5696-ad3b-64d7-0620975116e2@intel.com \
    --to=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=arnaldo.melo@gmail.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).