From: Thomas Richter <tmricht@linux.ibm.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: "linux-perf-use." <linux-perf-users@vger.kernel.org>,
ashelat@redhat.com, Michael Petlan <mpetlan@redhat.com>
Subject: Re: perf script: perf script hangs forever in linux-next
Date: Fri, 14 Feb 2025 11:21:56 +0100 [thread overview]
Message-ID: <b8b12ca5-28bd-4e17-923a-f4f5853b999a@linux.ibm.com> (raw)
In-Reply-To: <Z66mwEOy06-6hvO_@google.com>
On 2/14/25 03:13, Namhyung Kim wrote:
> perf script flamegraph -a -F 99 sleep 1
Thanks Namhyung,
i have tested your patch and both invocations of the perf script command
work again as can be seen here:
# perf script flamegraph -a -- sleep 1
dumping data to flamegraph.html
# perf record -- dd if=/dev/zero of=/dev/null bs=1M count=10K > /dev/null
10240+0 records in
10240+0 records out
10737418240 bytes (11 GB, 10 GiB) copied, 0.294051 s, 36.5 GB/s
[ perf record: Woken up 1 times to write data ]
[ perf record: Captured and wrote 0.060 MB perf.data (1177 samples) ]
# perf script report flamegraph
dumping data to flamegraph.html
#
Tested-by: Thomas Richter <tmricht@linux.ibm.com>
--
Thomas Richter, Dept 3303, IBM s390 Linux Development, Boeblingen, Germany
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2025-02-14 10:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-13 11:06 perf script: perf script hangs forever in linux-next Thomas Richter
2025-02-14 2:13 ` Namhyung Kim
2025-02-14 10:21 ` Thomas Richter [this message]
2025-02-19 10:13 ` PING " Thomas Richter
2025-02-19 20:34 ` Namhyung Kim
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=b8b12ca5-28bd-4e17-923a-f4f5853b999a@linux.ibm.com \
--to=tmricht@linux.ibm.com \
--cc=ashelat@redhat.com \
--cc=linux-perf-users@vger.kernel.org \
--cc=mpetlan@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).