From: David Hildenbrand <david@redhat.com>
To: Lance Yang <ioworker0@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Mingzhe Yang <mingzhe.yang@ly.com>
Subject: Re: [PATCH 1/1] mm/rmap: add CONFIG_MM_ID guard for folio_test_large_maybe_mapped_shared()
Date: Fri, 18 Apr 2025 12:38:33 +0200 [thread overview]
Message-ID: <413657ae-8271-4a5a-9507-e9161d1f08c2@redhat.com> (raw)
In-Reply-To: <CAK1f24nCWXgOonOpiJ0mEk+-rvGt4WN20yri+wi6-eMf3rf=4w@mail.gmail.com>
On 18.04.25 09:26, Lance Yang wrote:
> Hi Andrew,
>
> Thanks for taking the time to review!
>
> On Fri, Apr 18, 2025 at 6:02 AM Andrew Morton <akpm@linux-foundation.org> wrote:
>>
>> On Thu, 17 Apr 2025 20:49:08 +0800 Lance Yang <ioworker0@gmail.com> wrote:
>>
>>> Add a compile-time check to make sure folio_test_large_maybe_mapped_shared()
>>> is only used with CONFIG_MM_ID enabled, as it directly accesses the _mm_ids
>>> field that only works under CONFIG_MM_ID.
>>>
>>> ...
>>>
>>> --- a/include/linux/page-flags.h
>>> +++ b/include/linux/page-flags.h
>>> @@ -1232,6 +1232,8 @@ static inline int folio_has_private(const struct folio *folio)
>>>
>>> static inline bool folio_test_large_maybe_mapped_shared(const struct folio *folio)
>>> {
>>> + /* This function should never be called without CONFIG_MM_ID enabled. */
>>> + BUILD_BUG_ON(!IS_ENABLED(CONFIG_MM_ID));
>>> return test_bit(FOLIO_MM_IDS_SHARED_BITNUM, &folio->_mm_ids);
>>> }
>>> #undef PF_ANY
>>
>> I don't get it. Sounds like we're adding a compile-time check to check
>> for a compilation error which would have happened anyway.
>>
>> If folio_test_large_maybe_mapped_shared() is only used with
>> CONFIG_MM_ID enabled, then do
>>
>> #ifdef CONFIG_MM_ID
>> static inline bool folio_test_large_maybe_mapped_shared(...)
>> {
>> }
>> #endif
>>
>> ?
>
> Hmm... we considered using '#ifdef CONFIG_MM_ID' for
> folio_test_large_maybe_mapped_shared(),
> but since this function should never be called without CONFIG_MM_ID
> enabled, compile-time errors might be the way to go -- and a compile-time
> check here does the trick ;)
Yeah, I deliberately used plenty of IS_ENABLED to avoid a #ifdef mess
all over the place.
Maybe clarify in the patch description that we want to prevent the
function from getting used without CONFIG_MM_ID, and we don't want to
use #ifdef because then we'd have to add even more #ifdef in callers
that use IS_ENABLED(CONFIG_MM_ID).
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-04-18 10:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 12:49 Lance Yang
2025-04-17 12:56 ` David Hildenbrand
2025-04-17 13:24 ` Lance Yang
2025-04-17 13:26 ` David Hildenbrand
2025-04-17 14:29 ` Lance Yang
2025-04-17 22:02 ` Andrew Morton
2025-04-18 7:26 ` Lance Yang
2025-04-18 10:38 ` David Hildenbrand [this message]
2025-04-18 11:40 ` Lance Yang
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=413657ae-8271-4a5a-9507-e9161d1f08c2@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingzhe.yang@ly.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