[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4094f781edeb87b38594d54dbfeec674ebaf1b13.camel@nvidia.com>
Date: Wed, 7 Jan 2026 11:47:43 +0000
From: Cosmin Ratiu <cratiu@...dia.com>
To: "kuba@...nel.org" <kuba@...nel.org>
CC: "andrew+netdev@...n.ch" <andrew+netdev@...n.ch>, "davem@...emloft.net"
<davem@...emloft.net>, "linux-kselftest@...r.kernel.org"
<linux-kselftest@...r.kernel.org>, "shuah@...nel.org" <shuah@...nel.org>,
"pabeni@...hat.com" <pabeni@...hat.com>, "netdev@...r.kernel.org"
<netdev@...r.kernel.org>, "edumazet@...gle.com" <edumazet@...gle.com>,
Carolina Jubran <cjubran@...dia.com>
Subject: Re: [PATCH net-next 2/2] selftests: drv-net: psp: Don't fail
psp_responder when no PSP devs found
On Mon, 2026-01-05 at 17:52 -0800, Jakub Kicinski wrote:
> On Mon, 5 Jan 2026 12:04:24 +0200 Cosmin Ratiu wrote:
>
> > Change psp_responder to open the server socket and listen for
> > control
> > connections normally, and leave the skipping of the various test
> > cases
> > which require a PSP device (~most, but not all of them) to the
> > parent
> > test. This results in output like:
> >
> > ok 1 psp.test_case # SKIP No PSP devices found
> > [...]
> > ok 12 psp.dev_get_device # SKIP No PSP devices found
> > ok 13 psp.dev_get_device_bad
> > ok 14 psp.dev_rotate # SKIP No PSP devices found
> > [...]
>
> To be clear - in this case the DUT also doesn't have a PSP device?
> I'm struggling to connect the dots on how this error msg could come
> from psp_responder.
This happens when one runs the psp selftest against a DUT with PSP
disabled (e.g. no PSP devices present, or cap bits off or something
else not working).
This patch makes psp_responder not fail in this case, establish the
control connection and let the parent test determine which test cases
to run.
Cosmin.
Powered by blists - more mailing lists