netdev - Re: [PATCH net-next v2 11/12] selftests: ncdevmem: Move ncdevmem under drivers/net/hw

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAHS8izN6ePwKyRLtn2pdZjZwCQd6gyE_3OU2QvGRg0r9=2z3rw@mail.gmail.com>
Date: Thu, 3 Oct 2024 00:29:17 -0700
From: Mina Almasry <almasrymina@...gle.com>
To: Stanislav Fomichev <sdf@...ichev.me>
Cc: netdev@...r.kernel.org, davem@...emloft.net, edumazet@...gle.com, 
	kuba@...nel.org, pabeni@...hat.com
Subject: Re: [PATCH net-next v2 11/12] selftests: ncdevmem: Move ncdevmem
 under drivers/net/hw

On Mon, Sep 30, 2024 at 10:18 AM Stanislav Fomichev <sdf@...ichev.me> wrote:
>
> This is where all the tests that depend on the HW functionality live in
> and this is where the automated test is gonna be added in the next
> patch.
>

Tbh I don't like this very much. I wanted to take ncdevmem in the
opposite direction: to make at least the control path tests runnable
on netdevsim or something like that and have it not require any HW
support at all.

But I see in the cover letter that Jakub himself asked for the move,
so if there is some strong reason to make this in hw, sure.

Does it being under HW preclude future improvements to making it a
non-HW dependent test?

-- 
Thanks,
Mina