From: Alexei Starovoitov <ast@plumgrid.com>
To: Nicolas Schichan <nschichan@freebox.fr>,
Daniel Borkmann <daniel@iogearbox.net>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2 net-next 4/6] test_bpf: add module parameters to filter the tests to run.
Date: Tue, 4 Aug 2015 08:46:37 -0700 [thread overview]
Message-ID: <55C0DE5D.3040904@plumgrid.com> (raw)
In-Reply-To: <1438694352-17469-5-git-send-email-nschichan@freebox.fr>
On 8/4/15 6:19 AM, Nicolas Schichan wrote:
> When developping on the interpreter or a particular JIT, it can be
> interesting to restrict the tests list to a specific test or a
> particular range of tests.
>
> This patch adds the following module parameters to the test_bpf module:
>
> * test_name=<string>: only the specified named test will be run.
>
> * test_id=<number>: only the test with the specified id will be run
> (see the output of test_bpf without parameters to get the test id).
>
> * test_range=<number>,<number>: only the tests within IDs in the
> specified id range are run (see the output of test_bpf without
> parameters to get the test ids).
>
> Any invalid range, test id or test name will result in -EINVAL being
> returned and no tests being run.
>
> Signed-off-by: Nicolas Schichan<nschichan@freebox.fr>
> Acked-by: Daniel Borkmann<daniel@iogearbox.net>
looks good. thank you for adding range feature :)
Acked-by: Alexei Starovoitov <ast@plumgrid.com>
next prev parent reply other threads:[~2015-08-04 15:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 13:19 [PATCH V2 net-next 0/6] test_bpf improvements Nicolas Schichan
2015-08-04 13:19 ` [PATCH V2 net-next 1/6] test_bpf: avoid oopsing the kernel when generate_test_data() fails Nicolas Schichan
2015-08-04 13:19 ` [PATCH V2 net-next 2/6] test_bpf: allow tests to specify an skb fragment Nicolas Schichan
2015-08-04 13:19 ` [PATCH V2 net-next 3/6] test_bpf: test LD_ABS and LD_IND instructions on fragmented skbs Nicolas Schichan
2015-08-04 13:19 ` [PATCH V2 net-next 4/6] test_bpf: add module parameters to filter the tests to run Nicolas Schichan
2015-08-04 15:46 ` Alexei Starovoitov [this message]
2015-08-04 13:19 ` [PATCH V2 net-next 5/6] test_bpf: add more tests for LD_ABS and LD_IND Nicolas Schichan
2015-08-04 13:19 ` [PATCH V2 net-next 6/6] test_bpf: add tests checking that JIT/interpreter sets A and X to 0 Nicolas Schichan
2015-08-07 5:02 ` [PATCH V2 net-next 0/6] test_bpf improvements David Miller
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=55C0DE5D.3040904@plumgrid.com \
--to=ast@plumgrid.com \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nschichan@freebox.fr \
/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).