linux-s390.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@linux.ibm.com>
To: Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>, linux-s390@vger.kernel.org
Subject: Re: [PATCH] trace-cmd: fix writing of uncompressed size
Date: Mon, 11 Jul 2022 11:06:35 +0200	[thread overview]
Message-ID: <yt9da69g5884.fsf@linux.ibm.com> (raw)
In-Reply-To: <CAPpZLN45rz5nTn-XixV_pozdxHQREZymP_Vp8PDQAPXRDwguXA@mail.gmail.com> (Tzvetomir Stoyanov's message of "Mon, 11 Jul 2022 11:55:34 +0300")

Hi,

Tzvetomir Stoyanov <tz.stoyanov@gmail.com> writes:

> On Mon, Jul 11, 2022 at 10:44 AM Sven Schnelle <svens@linux.ibm.com> wrote:
>>
>> Pass &size instead of &handle->pointer. Interestingly this doesn't hurt
>> on x86, but makes trace-cmd fail on s390.
>
> Hi Sven,
> Thanks for testing this code on s390, I've tested it only on x86.
> Please, can you give more information about the trace-cmd failure on
> s390?

I'm running:

# trace-cmd record -p function -F /bin/ls
  plugin 'function'
[ls output follows]
CPU22 data recorded at offset=0x154000
    115345 bytes in size (1269760 uncompressed)
[skipped other CPUs, they didn't record anything]

trace-cmd report doesn't show any trace:

# trace-cmd report
version = 7

trace-cmd dump says:

# trace-cmd dump
 Tracing meta data in file trace.dat:
        [Initial format]
                7       [Version]
                1       [Big endian]
                8       [Bytes in a long]
                4096    [Page size, bytes]
                zstd    [Compression algorithm]
                1.5.2   [Compression version]
        [buffer "", "local" clock, 4096 page size, 1 cpus, 115345 bytes flyrecord data]
        [142 options]
trace-cmd: Unknown error -22
  cannot uncompress section block

Thanks,
Sven

  reply	other threads:[~2022-07-11  9:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-11  7:44 [PATCH] trace-cmd: fix writing of uncompressed size Sven Schnelle
2022-07-11  8:55 ` Tzvetomir Stoyanov
2022-07-11  9:06   ` Sven Schnelle [this message]
2022-07-11  9:14   ` Sven Schnelle
2022-07-11  9:25     ` Tzvetomir Stoyanov
2022-07-11  9:34       ` Sven Schnelle
  -- strict thread matches above, loose matches on Subject: below --
2022-07-11 18:21 [PATCH] trace-cmd: Fix " Steven Rostedt

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=yt9da69g5884.fsf@linux.ibm.com \
    --to=svens@linux.ibm.com \
    --cc=linux-s390@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tz.stoyanov@gmail.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).