From: Yunsheng Lin <yunshenglin0825@gmail.com>
To: Mark Brown <broonie@kernel.org>, Yunsheng Lin <linyunsheng@huawei.com>
Cc: davem@davemloft.net, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Duyck <alexander.duyck@gmail.com>,
Linux-MM <linux-mm@kvack.org>,
Alexander Duyck <alexanderduyck@fb.com>,
Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org, Aishwarya.TCV@arm.com
Subject: Re: [PATCH net-next v23 1/7] mm: page_frag: add a test module for page_frag
Date: Sat, 16 Nov 2024 12:59:36 +0800 [thread overview]
Message-ID: <4f9de1ec-8679-408e-a2d6-5baeac1618d6@gmail.com> (raw)
In-Reply-To: <ZzdWuUgyAET1babn@finisterre.sirena.org.uk>
On 11/15/2024 10:12 PM, Mark Brown wrote:
...
>
>> make -C tools/testing/selftests/livepatch/test_modules/
>
> Ah, this one is actually using some framework support for building
> modules - it's putting the modules in a separate directory and using
> TEST_GEN_MODS_DIR. Crucially, though, it has guards which ensure that
> we don't try to build the modules if KDIR doesn't exist - you should
> follow that pattern.
Will add a checking whether to build the test modules around the
TEST_GEN_MODS_DIR setup to avoid rsync copy error when the test module
compiling need to be skipped.
>
>>> in the main kernel tree and enabled by the config file for the mm tests.
>
>> As discussed in [1], this module is not really a vaild kernel module by
>> returning '-EAGAIN', which is the main reason that it is setup in the
>> selftests instead of the main kernel tree.
>
> Sure, we have other test stuff in the main kernel.
>
>> As above, I am not sure if there is some elegant way to avoid the above error
>> in the selftest core, one possible way to avoid the above error is to skip
>> compiling like below as tools/testing/selftests/mm/test_page_frag.sh already
>> skip the testing for page_frag if the test module is not compiled:
>
> Since the tests currently don't build the test systems are by and by
> large not getting as far as trying to run anything, the entire mm suite
> is just getting skipped.
I just sent a fix for above, it would be good if you can test it if it
fixes the above problem.
I tested it with both latest net-next main kernel and older host kernel,
it seems to work.
1.
https://lore.kernel.org/lkml/20241116042314.100400-1-yunshenglin0825@gmail.com/
next prev parent reply other threads:[~2024-12-05 15:24 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 11:53 [PATCH net-next v23 0/7] Replace page_frag with page_frag_cache (Part-1) Yunsheng Lin
2024-10-28 11:53 ` [PATCH net-next v23 1/7] mm: page_frag: add a test module for page_frag Yunsheng Lin
2024-11-14 16:02 ` Mark Brown
2024-11-15 9:03 ` Yunsheng Lin
2024-11-15 14:12 ` Mark Brown
2024-11-15 22:34 ` Jakub Kicinski
2024-11-16 5:08 ` Yunsheng Lin
2024-11-16 4:59 ` Yunsheng Lin [this message]
2024-10-28 11:53 ` [PATCH net-next v23 2/7] mm: move the page fragment allocator from page_alloc into its own file Yunsheng Lin
2024-10-28 11:53 ` [PATCH net-next v23 3/7] mm: page_frag: use initial zero offset for page_frag_alloc_align() Yunsheng Lin
2025-01-23 19:15 ` Florian Fainelli
2025-01-24 9:52 ` Yunsheng Lin
2025-01-24 18:55 ` Florian Fainelli
2024-10-28 11:53 ` [PATCH net-next v23 4/7] mm: page_frag: avoid caller accessing 'page_frag_cache' directly Yunsheng Lin
2024-10-28 11:53 ` [PATCH net-next v23 5/7] xtensa: remove the get_order() implementation Yunsheng Lin
2024-10-28 11:53 ` [PATCH net-next v23 6/7] mm: page_frag: reuse existing space for 'size' and 'pfmemalloc' Yunsheng Lin
2024-10-28 11:53 ` [PATCH net-next v23 7/7] mm: page_frag: use __alloc_pages() to replace alloc_pages_node() Yunsheng Lin
2024-10-28 15:30 ` [PATCH net-next v23 0/7] Replace page_frag with page_frag_cache (Part-1) Alexander Duyck
2024-10-29 9:36 ` Yunsheng Lin
2024-10-29 15:45 ` Alexander Duyck
2024-11-05 23:57 ` Jakub Kicinski
2024-11-08 0:02 ` Alexander Duyck
2024-11-11 22:20 ` 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=4f9de1ec-8679-408e-a2d6-5baeac1618d6@gmail.com \
--to=yunshenglin0825@gmail.com \
--cc=Aishwarya.TCV@arm.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.duyck@gmail.com \
--cc=alexanderduyck@fb.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linyunsheng@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=shuah@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox