From: Adrian Hunter <adrian.hunter@intel.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Andi Kleen <ak@linux.intel.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Jiri Olsa <jolsa@redhat.com>, Ian Rogers <irogers@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 5/5] perf intel-pt: Support itrace option flag d+e to log on error
Date: Fri, 2 Sep 2022 15:01:01 +0300 [thread overview]
Message-ID: <bf500303-394a-4806-361a-7cc559d80e98@intel.com> (raw)
In-Reply-To: <CAM9d7chiutXEZfpQbayJ3bgraLZ_YFGC15yDn7sQBT4asdEfjA@mail.gmail.com>
On 2/09/22 04:34, Namhyung Kim wrote:
> On Thu, Sep 1, 2022 at 9:29 AM Adrian Hunter <adrian.hunter@intel.com> wrote:
>>
>> On 1/09/22 17:31, Andi Kleen wrote:
>>>
>>> On 9/1/2022 4:00 AM, Adrian Hunter wrote:
>
> [SNIP]
>>>> +
>>>> +static void log_buf__dump(struct log_buf *b)
>>>> +{
>>>> + if (!b->buf)
>>>> + return;
>>>> +
>>>> + fflush(f);
>>>> + fprintf(b->backend, "Dumping debug log buffer (first line may be sliced)\n");
>>>
>>>
>>> Should be easy to skip the first line, no?
>>
>> Not as easy as typing " (first line may be sliced)" ;-)
>>
>> Still not sure it is worth having the extra complication, but here
>> is the change as a separate patch:
>>
>> From: Adrian Hunter <adrian.hunter@intel.com>
>> Date: Thu, 1 Sep 2022 19:01:33 +0300
>> Subject: [PATCH] perf intel-pt: Remove first line of log dumped on error
>>
>> Instead of printing "(first line may be sliced)", always remove the
>> first line of the debug log when dumping on error.
>>
>> Signed-off-by: Adrian Hunter <adrian.hunter@intel.com>
>> ---
>> .../perf/util/intel-pt-decoder/intel-pt-log.c | 27 ++++++++++++++++---
>> 1 file changed, 24 insertions(+), 3 deletions(-)
>>
>> diff --git a/tools/perf/util/intel-pt-decoder/intel-pt-log.c b/tools/perf/util/intel-pt-decoder/intel-pt-log.c
>> index ea96dcae187a7..6cc465d1f7a9e 100644
>> --- a/tools/perf/util/intel-pt-decoder/intel-pt-log.c
>> +++ b/tools/perf/util/intel-pt-decoder/intel-pt-log.c
>> @@ -143,16 +143,37 @@ static FILE *log_buf__open(struct log_buf *b, FILE *backend, unsigned int sz)
>> return file;
>> }
>>
>> +static bool remove_first_line(const char **p, size_t *n)
>> +{
>> + for (; *n && **p != '\n'; ++*p, --*n)
>> + ;
>> + if (*n) {
>> + *p += 1;
>> + *n -= 1;
>> + return true;
>> + }
>> + return false;
>> +}
>> +
>> +static void write_lines(const char *p, size_t n, FILE *fp, bool *remove_first)
>> +{
>> + if (*remove_first)
>> + *remove_first = !remove_first_line(&p, &n);
>> + fwrite(p, n, 1, fp);
>> +}
>> +
>> static void log_buf__dump(struct log_buf *b)
>> {
>> + bool remove_first = true;
>
> Isn't it only required when the buf is wrapped?
Very true! Thanks for spotting that!
I will send a new version.
>
> Thanks,
> Namhyung
>
>
>> +
>> if (!b->buf)
>> return;
>>
>> fflush(f);
>> - fprintf(b->backend, "Dumping debug log buffer (first line may be sliced)\n");
>> + fprintf(b->backend, "Dumping debug log buffer\n");
>> if (b->wrapped)
>> - fwrite(b->buf + b->head, b->buf_sz - b->head, 1, b->backend);
>> - fwrite(b->buf, b->head, 1, b->backend);
>> + write_lines(b->buf + b->head, b->buf_sz - b->head, b->backend, &remove_first);
>> + write_lines(b->buf, b->head, b->backend, &remove_first);
>> fprintf(b->backend, "End of debug log buffer dump\n");
>>
>> b->head = 0;
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2022-09-02 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-01 11:00 [PATCH 0/5] " Adrian Hunter
2022-09-01 11:00 ` [PATCH 1/5] perf tools: Add perf_config_scan() Adrian Hunter
2022-09-01 11:00 ` [PATCH 2/5] perf auxtrace: Add itrace option flag d+e to log on error Adrian Hunter
2022-09-01 11:00 ` [PATCH 3/5] perf intel-pt: Improve man page layout slightly Adrian Hunter
2022-09-01 11:00 ` [PATCH 4/5] perf intel-pt: Improve object code read error message Adrian Hunter
2022-09-01 11:00 ` [PATCH 5/5] perf intel-pt: Support itrace option flag d+e to log on error Adrian Hunter
2022-09-01 14:31 ` Andi Kleen
2022-09-01 16:28 ` Adrian Hunter
2022-09-02 1:34 ` Namhyung Kim
2022-09-02 12:01 ` Adrian Hunter [this message]
2022-09-02 19:06 ` Arnaldo Carvalho de Melo
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=bf500303-394a-4806-361a-7cc559d80e98@intel.com \
--to=adrian.hunter@intel.com \
--cc=acme@kernel.org \
--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 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®