From: Song Liu <song@kernel.org>
To: <bpf@vger.kernel.org>, <linux-mm@kvack.org>
Cc: <akpm@linux-foundation.org>, <x86@kernel.org>,
<peterz@infradead.org>, <hch@lst.de>,
<rick.p.edgecombe@intel.com>, <aaron.lu@intel.com>,
<rppt@kernel.org>, <mcgrof@kernel.org>,
Song Liu <song@kernel.org>
Subject: [PATCH bpf-next v3 3/6] selftests/vm: extend test_vmalloc to test execmem_* APIs
Date: Wed, 16 Nov 2022 17:06:18 -0800 [thread overview]
Message-ID: <20221117010621.1891711-4-song@kernel.org> (raw)
In-Reply-To: <20221117010621.1891711-1-song@kernel.org>
Add logic to test execmem_[alloc|fill|free] in test_vmalloc.c.
No need to change tools/testing/selftests/vm/test_vmalloc.sh.
Signed-off-by: Song Liu <song@kernel.org>
---
lib/test_vmalloc.c | 30 ++++++++++++++++++++++++++++++
1 file changed, 30 insertions(+)
diff --git a/lib/test_vmalloc.c b/lib/test_vmalloc.c
index cf7780572f5b..6591c4932c3c 100644
--- a/lib/test_vmalloc.c
+++ b/lib/test_vmalloc.c
@@ -50,6 +50,7 @@ __param(int, run_test_mask, INT_MAX,
"\t\tid: 128, name: pcpu_alloc_test\n"
"\t\tid: 256, name: kvfree_rcu_1_arg_vmalloc_test\n"
"\t\tid: 512, name: kvfree_rcu_2_arg_vmalloc_test\n"
+ "\t\tid: 1024, name: execmem_alloc_test\n"
/* Add a new test case description here. */
);
@@ -352,6 +353,34 @@ kvfree_rcu_2_arg_vmalloc_test(void)
return 0;
}
+static int
+execmem_alloc_test(void)
+{
+ void *p, *tmp;
+ int i;
+
+ for (i = 0; i < test_loop_count; i++) {
+ /* allocate variable size, up to 64kB */
+ size_t size = (i % 1024 + 1) * 64;
+
+ p = execmem_alloc(size, 64);
+ if (!p)
+ return -1;
+
+ tmp = execmem_fill(p, "a", 1);
+ if (tmp != p)
+ return -1;
+
+ tmp = execmem_fill(p + size - 1, "b", 1);
+ if (tmp != p + size - 1)
+ return -1;
+
+ execmem_free(p);
+ }
+
+ return 0;
+}
+
struct test_case_desc {
const char *test_name;
int (*test_func)(void);
@@ -368,6 +397,7 @@ static struct test_case_desc test_case_array[] = {
{ "pcpu_alloc_test", pcpu_alloc_test },
{ "kvfree_rcu_1_arg_vmalloc_test", kvfree_rcu_1_arg_vmalloc_test },
{ "kvfree_rcu_2_arg_vmalloc_test", kvfree_rcu_2_arg_vmalloc_test },
+ { "execmem_alloc_test", execmem_alloc_test },
/* Add a new test case here. */
};
--
2.30.2
next prev parent reply other threads:[~2022-11-17 1:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 1:06 [PATCH bpf-next v3 0/6] execmem_alloc for BPF programs Song Liu
2022-11-17 1:06 ` [PATCH bpf-next v3 1/6] vmalloc: introduce execmem_alloc, execmem_free, and execmem_fill Song Liu
2022-11-17 1:36 ` Luis Chamberlain
2022-11-17 6:48 ` Song Liu
2022-11-17 1:06 ` [PATCH bpf-next v3 2/6] x86/alternative: support execmem_alloc() and execmem_free() Song Liu
2022-11-17 1:06 ` Song Liu [this message]
2022-11-17 1:49 ` [PATCH bpf-next v3 3/6] selftests/vm: extend test_vmalloc to test execmem_* APIs Luis Chamberlain
2022-11-17 6:41 ` Song Liu
2022-11-17 20:04 ` Luis Chamberlain
2022-11-17 1:06 ` [PATCH bpf-next v3 4/6] bpf: use execmem_alloc for bpf program and bpf dispatcher Song Liu
2022-11-17 1:52 ` Luis Chamberlain
2022-11-17 2:10 ` Alexei Starovoitov
2022-11-17 20:01 ` Luis Chamberlain
2022-11-17 20:03 ` Luis Chamberlain
2022-11-17 1:06 ` [PATCH bpf-next v3 5/6] vmalloc: introduce register_text_tail_vm() Song Liu
2022-11-17 1:06 ` [PATCH bpf-next v3 6/6] x86: use register_text_tail_vm Song Liu
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=20221117010621.1891711-4-song@kernel.org \
--to=song@kernel.org \
--cc=aaron.lu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bpf@vger.kernel.org \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=mcgrof@kernel.org \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=rppt@kernel.org \
--cc=x86@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.