All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
	Jiri Olsa <jolsa@redhat.com>, Ian Rogers <irogers@google.com>,
	Andi Kleen <ak@linux.intel.com>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V2 0/6] perf intel-pt: Support itrace option flag d+e to log on error
Date: Thu, 8 Sep 2022 16:09:07 -0300	[thread overview]
Message-ID: <Yxo903EQ74Xl94DR@kernel.org> (raw)
In-Reply-To: <CAM9d7cg8fTPTSzcZiwgQE4eF6HdpkuZ+YkQ=fAb+iB80V8nQEw@mail.gmail.com>

Em Tue, Sep 06, 2022 at 10:24:03AM -0700, Namhyung Kim escreveu:
> HI Arnaldo,
> 
> On Tue, Sep 6, 2022 at 6:05 AM Arnaldo Carvalho de Melo <acme@kernel.org> wrote:
> >
> > Em Mon, Sep 05, 2022 at 10:34:18AM +0300, Adrian Hunter escreveu:
> > > Hi
> > >
> > > Here are a few patches to add the ability to output the decoding debug log
> > > only when there are decoding errors.
> > >
> > > This is motivated by the fact that a full log can be very large, so just
> > > getting interesting bits is useful for analyzing errors.
> > >
> > > If necessary, the size of output on error is configurable via perf config,
> > > and perf_config_scan() was added in the 1st patch to make that simpler.
> > >
> > > The 2nd patch adds the new option flag to auxtrace.
> > >
> > > There are a couple of very minor and essentially unrelated changes in
> > > patches 3 and 4.
> > >
> > > The main Intel PT change is in patch 5 and there is a small example in the
> > > commit message.
> > >
> > >
> > > Changes in V2:
> > >
> > >       perf intel-pt: Support itrace option flag d+e to log on error
> > >       Ensure log_buf is defined before use
> > >
> > >       perf intel-pt: Remove first line of log dumped on error
> > >       Remove first line only if the buffer has wrapped
> >
> > Applied locally, Namhyung: I think your review comment was addressed,
> > right? If so can I add your Reviewed-by to all the patches in this
> > series?
> 
> Sure,
> 
> Reviewed-by: Namhyung Kim <namhyung@kernel.org>

Thanks, added.

- Arnaldo


      reply	other threads:[~2022-09-08 19:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-05  7:34 [PATCH V2 0/6] perf intel-pt: Support itrace option flag d+e to log on error Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 1/6] perf tools: Add perf_config_scan() Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 2/6] perf auxtrace: Add itrace option flag d+e to log on error Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 3/6] perf intel-pt: Improve man page layout slightly Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 4/6] perf intel-pt: Improve object code read error message Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 5/6] perf intel-pt: Support itrace option flag d+e to log on error Adrian Hunter
2022-09-05  7:34 ` [PATCH V2 6/6] perf intel-pt: Remove first line of log dumped " Adrian Hunter
2022-09-06 13:05 ` [PATCH V2 0/6] perf intel-pt: Support itrace option flag d+e to log " Arnaldo Carvalho de Melo
2022-09-06 17:24   ` Namhyung Kim
2022-09-08 19:09     ` 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=Yxo903EQ74Xl94DR@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=irogers@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=namhyung@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.