linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: "Steinar H. Gunderson" <sesse@google.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@redhat.com>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] perf intel-pt: Synthesize cycle events
Date: Fri, 17 Feb 2023 11:03:49 -0300	[thread overview]
Message-ID: <Y++JRY4ExBkxeejU@kernel.org> (raw)
In-Reply-To: <Y+9evQVBRLrCLQKf@google.com>

Em Fri, Feb 17, 2023 at 12:02:21PM +0100, Steinar H. Gunderson escreveu:
> On Fri, Mar 25, 2022 at 07:07:40PM -0300, Arnaldo Carvalho de Melo wrote:
> >>> 
> >>> There are two issues in play:
> >>> 
> >>>  1. PT event synth doesn't support reading inline information from DWARF
> >>>     yet, and my patch to add it runs into some problems. This is not
> >>>     relevant for this patch at all.
> >>>  2. The results from v3 don't quite match the ones from v1, and neither
> >>>     of us are entirely sure why. My personal feeling is that the one
> >>>     from v1 are the wrong ones, but it's up to Adrian to say whether we
> >>>     want to try to investigate deeply here.
> >> V3 is good.  Please take that.
> > Thanks, applied.
> 
> Hi,
> 
> I downloaded linux-6.1.12 now and built perf from that, and this patch
> isn't included. Did it get somehow lost along the way?

I must have committed some mistake when doing rebases, I'm sorry.

I applied it now and will push it later today, after the usual set of
tests with it and other patches I apply today.

- Arnaldo

      reply	other threads:[~2023-02-17 14:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-22  8:24 [PATCH v3] perf intel-pt: Synthesize cycle events Steinar H. Gunderson
2022-03-22 21:32 ` Arnaldo Carvalho de Melo
2022-03-22 21:53   ` Steinar H. Gunderson
2022-03-23  7:58     ` Adrian Hunter
2022-03-25 22:07       ` Arnaldo Carvalho de Melo
2023-02-17 11:02         ` Steinar H. Gunderson
2023-02-17 14:03           ` Arnaldo Carvalho de Melo [this message]

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=Y++JRY4ExBkxeejU@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sesse@google.com \
    /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).