linux-kernel - Re: [PATCH 1/2] rtla/timerlat: Make timerlat_top_cpu->*

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAP4=nvR+RML-=owASqjqQvhn1ernCP5QtREcPU=FLiOZ5G-RBA@mail.gmail.com>
Date: Mon, 14 Oct 2024 10:57:38 +0200
From: Tomas Glozar <tglozar@...hat.com>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: linux-trace-kernel@...r.kernel.org, linux-kernel@...r.kernel.org, 
	jkacur@...hat.com, lgoncalv@...hat.com, Attila Fazekas <afazekas@...hat.com>
Subject: Re: [PATCH 1/2] rtla/timerlat: Make timerlat_top_cpu->*_count
 unsigned long long

pá 11. 10. 2024 v 19:23 odesílatel Steven Rostedt <rostedt@...dmis.org> napsal:
>
> Thanks, I'm applying these, but could you or someone else create a test
> directory in rtla and even rv that tests this code. I just examine it and
> run some basic operations, but I have no idea if it is really working or not.
>
> Having a utest directory or something would be really beneficial. That way,
> I can at least run that test before I push it up to my tree.
>

Yeah, we definitely need that, ideally to test expected behavior for
each common set of command line options. That would prevent unexpected
changes, like the recent defaulting to userspace threads requiring -k
to be used together with -U, otherwise, -U has no effect (because -u
is added by default). I'll look into that.

Tomas