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: <20250723102245.75631501@batman.local.home>
Date: Wed, 23 Jul 2025 10:22:45 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Gabriele Monaco <gmonaco@...hat.com>
Cc: linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...hat.com>, Peter
 Zijlstra <peterz@...radead.org>, Nam Cao <namcao@...utronix.de>, Tomas
 Glozar <tglozar@...hat.com>, Juri Lelli <jlelli@...hat.com>, Clark Williams
 <williams@...hat.com>, John Kacur <jkacur@...hat.com>
Subject: Re: [PATCH v4 00/14] rv: Add monitors to validate task switch

On Wed, 23 Jul 2025 11:55:50 +0200
Gabriele Monaco <gmonaco@...hat.com> wrote:

> The rationale is that tools files changed in the kernel patches are not
> really tool stuff (dot models). And kernel stuff changed in the tools
> are something that the tools generate, and to test them a build should
> suffice (kernel robot would do that). Having them together eases
> testing the tool, I believe.

Yes, I agree with the above.

If you make kernel changes that a new dot file is going to use, then
sure, keep that in the kernel side.

I'm basically saying that any tools enhancements beyond adding new
models and such should be in their own series.

Thanks,

-- Steve

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ