From: Adrian Hunter <adrian.hunter@intel.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, Andi Kleen <ak@linux.intel.com>
Subject: Re: [PATCH 1/2] perf intel-pt-decoder: Report instruction bytes and length in sample
Date: Fri, 7 Oct 2016 16:45:18 +0300 [thread overview]
Message-ID: <f3d9e2ea-39ac-365c-6147-39348c0b5a32@intel.com> (raw)
In-Reply-To: <20161005113613.GW7143@kernel.org>
On 05/10/16 14:36, Arnaldo Carvalho de Melo wrote:
> Em Mon, Oct 03, 2016 at 05:30:32PM -0700, Andi Kleen escreveu:
>> From: Andi Kleen <ak@linux.intel.com>
>>
>> Change the Intel PT decoder to pass up the length and the instruction
>> bytes of the decoded or sampled instruction in the perf sample.
>>
>> The decoder already knows this information, we just need to pass it
>> up. Since it is only a couple of movs it is not very expensive.
>>
>> Used in the next patch.
>
> Adrian, Ack?
I did a little tidy-up in Intel PT / BTS and re-based Andi's patch with my
SOB. Please see V3 patch I sent.
next prev parent reply other threads:[~2016-10-07 13:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-04 0:30 Andi Kleen
2016-10-04 0:30 ` [PATCH 2/2] perf tools: Support insn and insnlen in perf script Andi Kleen
2016-10-05 11:36 ` [PATCH 1/2] perf intel-pt-decoder: Report instruction bytes and length in sample Arnaldo Carvalho de Melo
2016-10-07 13:45 ` Adrian Hunter [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-09-30 3:49 Andi Kleen
2016-09-30 10:07 ` Adrian Hunter
2016-10-04 0:33 ` Andi Kleen
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=f3d9e2ea-39ac-365c-6147-39348c0b5a32@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®