From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>,
Yordan Karadzhov <y.karadz@gmail.com>,
Tzvetomir Stoyanov <tz.stoyanov@gmail.com>
Subject: Re: Issue with trace-cmd 3 and kernelshark
Date: Sat, 12 Mar 2022 00:06:08 -0500 [thread overview]
Message-ID: <20220312000608.58342480@gandalf.local.home> (raw)
In-Reply-To: <20220311235044.6e416b48@gandalf.local.home>
On Fri, 11 Mar 2022 23:50:44 -0500
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Fri, 11 Mar 2022 22:18:25 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
> > It appears that it doesn't like the fact that the file is compressed. This
> > was my worry about compressing date :-/
>
> Actually, it doesn't look like this is an issue with compression, but the
> fact that the cpu involved doesn't have any data, and we no longer save
> anything for that case.
>
> The problem data is here:
> https://rostedt.org/private/trace-data/gentoo/trace.dat
> https://rostedt.org/private/trace-data/gentoo/trace-gentoo.dat
>
> And do a: kernelshark trace.dat -a trace-gentoo.dat
>
Actually, it's just the trace.dat file that crashes in kernelshark.
As the number of CPUs that have data is only 35 (and thus handle->cpus is
just 35) but the box I ran this on has 128 CPUs.
There needs to be a generic way to map the actual CPU to the one saved in
the file. the cpu_data[cpu] won't work if the cpu_data array does not
contain CPUs that exist on the machine.
-- Steve
prev parent reply other threads:[~2022-03-12 5:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-12 3:18 Issue with trace-cmd 3 and kernelshark Steven Rostedt
2022-03-12 4:50 ` Steven Rostedt
2022-03-12 5:06 ` Steven Rostedt [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=20220312000608.58342480@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=tz.stoyanov@gmail.com \
--cc=y.karadz@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).