Message ID | 20241107181211.3934153-1-sdf@fomichev.me |
---|---|
Headers | show |
Series | selftests: ncdevmem: Add ncdevmem to ksft | expand |
On Thu, Nov 07, 2024 at 10:12:11AM -0800, Stanislav Fomichev wrote: > Only RX side for now and small message to test the setup. > In the future, we can extend it to TX side and to testing > both sides with a couple of megs of data. > > make \ > -C tools/testing/selftests \ > TARGETS="drivers/hw/net" \ > install INSTALL_PATH=~/tmp/ksft > > scp ~/tmp/ksft ${HOST}: > scp ~/tmp/ksft ${PEER}: > > cfg+="NETIF=${DEV}\n" > cfg+="LOCAL_V6=${HOST_IP}\n" > cfg+="REMOTE_V6=${PEER_IP}\n" > cfg+="REMOTE_TYPE=ssh\n" > cfg+="REMOTE_ARGS=root@${PEER}\n" > > echo -e "$cfg" | ssh root@${HOST} "cat > ksft/drivers/net/net.config" > ssh root@${HOST} "cd ksft && ./run_kselftest.sh -t drivers/net:devmem.py" > > Reviewed-by: Mina Almasry <almasrymina@google.com> > Signed-off-by: Stanislav Fomichev <sdf@fomichev.me> > --- > .../testing/selftests/drivers/net/hw/Makefile | 1 + > .../selftests/drivers/net/hw/devmem.py | 45 +++++++++++++++++++ > 2 files changed, 46 insertions(+) > create mode 100755 tools/testing/selftests/drivers/net/hw/devmem.py I'm not a python expert, but the changes make sense to me. Reviewed-by: Joe Damato <jdamato@fastly.com>
On 11/07, Joe Damato wrote: > On Thu, Nov 07, 2024 at 10:11:59AM -0800, Stanislav Fomichev wrote: > > The goal of the series is to simplify and make it possible to use > > ncdevmem in an automated way from the ksft python wrapper. > > > > ncdevmem is slowly mutated into a state where it uses stdout > > to print the payload and the python wrapper is added to > > make sure the arrived payload matches the expected one. > > > > v8: > > - move error() calls into enable_reuseaddr() (Joe) > > - bail out when number of queues is 1 (Joe) > > Thanks for all the work on the refactor; sorry for the nit-picking > on the queue counts. I just thought of it because in my test for > busy poll stuff, netdevsim uses 1 queue. > > Having tests like this factored nicely really helps when people > (like me) go to try to write a test for the first time and have a > good example like this to follow :) No worries, thanks for taking the time to review! nit-picks are fine as wells since they are usually the easiest ones to address :-D