From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Adrian Hunter <adrian.hunter@intel.com>
Cc: Jiri Olsa <jolsa@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] perf intel-pt: Fixes
Date: Fri, 10 Dec 2021 15:40:00 -0300 [thread overview]
Message-ID: <YbOfALOv1L5AYk9g@kernel.org> (raw)
In-Reply-To: <20211210162303.2288710-1-adrian.hunter@intel.com>
Em Fri, Dec 10, 2021 at 06:22:56PM +0200, Adrian Hunter escreveu:
> Hi
>
> Here are a few fairly small Intel PT fixes. Backports would be needed
> to apply before v5.15, so the stable tags reflect that.
>
Thanks, applied.
- Arnaldo
> Adrian Hunter (7):
> perf intel-pt: Fix some PGE usage
> perf intel-pt: Fix sync state
> perf intel-pt: Fix intel_pt_fup_event() assumptions
> perf intel-pt: Fix overflow state
> perf intel-pt: Fix next 'err' value, walking trace
> perf intel-pt: Fix missing 'instruction' events with 'q' option
> perf intel-pt: Fix error timestamp
>
> .../perf/util/intel-pt-decoder/intel-pt-decoder.c | 85 ++++++++++++++--------
> tools/perf/util/intel-pt.c | 1 +
> 2 files changed, 56 insertions(+), 30 deletions(-)
>
>
> Regards
> Adrian
--
- Arnaldo
prev parent reply other threads:[~2021-12-10 18:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 16:22 [PATCH 0/7] perf intel-pt: Fixes Adrian Hunter
2021-12-10 16:22 ` [PATCH 1/7] perf intel-pt: Fix some PGE usage Adrian Hunter
2021-12-10 16:22 ` [PATCH 2/7] perf intel-pt: Fix sync state Adrian Hunter
2021-12-10 16:22 ` [PATCH 3/7] perf intel-pt: Fix intel_pt_fup_event() assumptions Adrian Hunter
2021-12-10 16:23 ` [PATCH 4/7] perf intel-pt: Fix overflow state Adrian Hunter
2021-12-10 16:23 ` [PATCH 5/7] perf intel-pt: Fix next 'err' value, walking trace Adrian Hunter
2021-12-10 16:23 ` [PATCH 6/7] perf intel-pt: Fix missing 'instruction' events with 'q' option Adrian Hunter
2021-12-10 16:23 ` [PATCH 7/7] perf intel-pt: Fix error timestamp Adrian Hunter
2021-12-10 18:40 ` 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=YbOfALOv1L5AYk9g@kernel.org \
--to=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=jolsa@redhat.com \
--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