From: Benjamin Poirier <bpoirier@nvidia.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org, kuba@kernel.org, pabeni@redhat.com,
davem@davemloft.net, edumazet@google.com, parav@nvidia.com,
mst@redhat.com, jasowang@redhat.com, xuanzhuo@linux.alibaba.com,
shuah@kernel.org, petrm@nvidia.com, liuhangbin@gmail.com,
vladimir.oltean@nxp.com, idosch@nvidia.com,
virtualization@lists.linux.dev
Subject: Re: [patch net-next v6 5/5] selftests: virtio_net: add initial tests
Date: Wed, 24 Apr 2024 11:29:53 -0400 [thread overview]
Message-ID: <ZiklcfBlSWhyew7c@f4> (raw)
In-Reply-To: <20240424104049.3935572-6-jiri@resnulli.us>
On 2024-04-24 12:40 +0200, Jiri Pirko wrote:
> From: Jiri Pirko <jiri@nvidia.com>
>
> Introduce initial tests for virtio_net driver. Focus on feature testing
> leveraging previously introduced debugfs feature filtering
> infrastructure. Add very basic ping and F_MAC feature tests.
>
> To run this, do:
> $ make -C tools/testing/selftests/ TARGETS=drivers/net/virtio_net/ run_tests
>
> Run it on a system with 2 virtio_net devices connected back-to-back
> on the hypervisor.
>
> Signed-off-by: Jiri Pirko <jiri@nvidia.com>
> Reviewed-by: Petr Machata <petrm@nvidia.com>
> ---
Tested-by: Benjamin Poirier <bpoirier@nvidia.com>
next prev parent reply other threads:[~2024-04-24 15:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-24 10:40 [patch net-next v6 0/5] selftests: virtio_net: introduce initial testing infrastructure Jiri Pirko
2024-04-24 10:40 ` [patch net-next v6 1/5] virtio: add debugfs infrastructure to allow to debug virtio features Jiri Pirko
2024-04-24 10:40 ` [patch net-next v6 2/5] selftests: forwarding: add ability to assemble NETIFS array by driver name Jiri Pirko
2024-04-24 15:27 ` Benjamin Poirier
2024-04-24 10:40 ` [patch net-next v6 3/5] selftests: forwarding: add check_driver() helper Jiri Pirko
2024-04-24 15:28 ` Benjamin Poirier
2024-04-24 10:40 ` [patch net-next v6 4/5] selftests: forwarding: add wait_for_dev() helper Jiri Pirko
2024-04-24 15:28 ` Benjamin Poirier
2024-04-24 10:40 ` [patch net-next v6 5/5] selftests: virtio_net: add initial tests Jiri Pirko
2024-04-24 15:29 ` Benjamin Poirier [this message]
2024-04-26 11:40 ` [patch net-next v6 0/5] selftests: virtio_net: introduce initial testing infrastructure patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZiklcfBlSWhyew7c@f4 \
--to=bpoirier@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=jasowang@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=liuhangbin@gmail.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=petrm@nvidia.com \
--cc=shuah@kernel.org \
--cc=virtualization@lists.linux.dev \
--cc=vladimir.oltean@nxp.com \
--cc=xuanzhuo@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).