Re: Issue with trace-cmd 3 and kernelshark

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, 11 Mar 2022 23:50:44 -0500
Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

> On Fri, 11 Mar 2022 22:18:25 -0500
> Steven Rostedt <rostedt@xxxxxxxxxxx> 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




[Index of Archives]     [Linux USB Development]     [Linux USB Development]     [Linux Audio Users]     [Yosemite Hiking]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux