From: Luis Chamberlain <mcgrof@kernel.org>
To: akpm@linux-foundation.org, willy@infradead.org, Liam.Howlett@oracle.com
Cc: linux-fsdevel@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, djwong@kernel.org,
david@fromorbit.com, gost.dev@samsung.com, p.raghav@samsung.com,
da.gomez@samsung.com, mcgrof@kernel.org
Subject: [PATCH 1/2] tools: fix userspace compilation with new test_xarray changes
Date: Tue, 23 Apr 2024 11:05:15 -0700 [thread overview]
Message-ID: <20240423180517.256812-2-mcgrof@kernel.org> (raw)
In-Reply-To: <20240423180517.256812-1-mcgrof@kernel.org>
Liam reported that compiling the test_xarray on userspace was broken.
I was not even aware that was possible but you can via and you can
run these tests in userspace with:
make -C tools/testing/radix-tree
./tools/testing/radix-tree/xarray
Add the two helpers we need to fix compilation. We don't need a
userspace schedule() so just make it do nothing.
Reported-by: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Signed-off-by: Luis Chamberlain <mcgrof@kernel.org>
---
tools/testing/radix-tree/linux/kernel.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/testing/radix-tree/linux/kernel.h b/tools/testing/radix-tree/linux/kernel.h
index c5c9d05f29da..c0a2bb785b92 100644
--- a/tools/testing/radix-tree/linux/kernel.h
+++ b/tools/testing/radix-tree/linux/kernel.h
@@ -18,6 +18,8 @@
#define pr_info printk
#define pr_debug printk
#define pr_cont printk
+#define schedule()
+#define PAGE_SHIFT 12
#define __acquires(x)
#define __releases(x)
--
2.43.0
next prev parent reply other threads:[~2024-04-23 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-23 18:05 [PATCH 0/2] test_xarray: couple of fixes for v6-9-rc6 Luis Chamberlain
2024-04-23 18:05 ` Luis Chamberlain [this message]
2024-04-24 15:10 ` [PATCH 1/2] tools: fix userspace compilation with new test_xarray changes Liam R. Howlett
2024-04-23 18:05 ` [PATCH 2/2] lib/test_xarray.c: fix error assumptions on check_xa_multi_store_adv_add() Luis Chamberlain
2024-04-24 15:16 ` Liam R. Howlett
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=20240423180517.256812-2-mcgrof@kernel.org \
--to=mcgrof@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=da.gomez@samsung.com \
--cc=david@fromorbit.com \
--cc=djwong@kernel.org \
--cc=gost.dev@samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=p.raghav@samsung.com \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox