On 4/15/21 3:49 PM, Steven Rostedt wrote:
> OK, for osnoise, I can see how it is useful. But as you said above, for
> hwlat tracer, it's not as useful.
I agree, it is not as useful.
-- Daniel
On Thu, 15 Apr 2021 15:09:50 +0200
Daniel Bristot de Oliveira wrote:
> But for the osnoise tracer the cpus file is really useful. For instance, on a
> system with the CPU 7 isolated:
>
> - %< -
> # echo 7 > osnoise/cpus
> # echo target_cpu == 7 > events/sched/sched_wakeup/filter
>
On 4/14/21 4:10 PM, Steven Rostedt wrote:
> On Thu, 8 Apr 2021 16:13:19 +0200
> Daniel Bristot de Oliveira wrote:
>
>> Provides a "cpus" interface to the hardware latency detector. By
>> default, it lists all CPUs, allowing hwlatd threads to run on any online
>> CPU of the system.
>>
>> It
On Thu, 8 Apr 2021 16:13:19 +0200
Daniel Bristot de Oliveira wrote:
> Provides a "cpus" interface to the hardware latency detector. By
> default, it lists all CPUs, allowing hwlatd threads to run on any online
> CPU of the system.
>
> It serves to restrict the execution of hwlatd to the set of
Provides a "cpus" interface to the hardware latency detector. By
default, it lists all CPUs, allowing hwlatd threads to run on any online
CPU of the system.
It serves to restrict the execution of hwlatd to the set of CPUs writing
via this interface. Note that hwlatd also respects the
5 matches
Mail list logo
