From: Rik van Riel <riel@surriel.com>
To: Hou Wenlong <houwenlong.hwl@antgroup.com>, linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Jann Horn <jannh@google.com>, Barry Song <baohua@kernel.org>
Subject: Re: [PATCH] x86/mm: Hide mm_free_global_asid() definition under 'CONFIG_BROADCAST_TLB_FLUSH'
Date: Wed, 14 Jan 2026 10:09:42 -0500 [thread overview]
Message-ID: <733058ef2a54dc8323835fc26ca3b402ced5fc7f.camel@surriel.com> (raw)
In-Reply-To: <f5b5021cd1936127ba73b9d62ff7a975260c70eb.1768396374.git.houwenlong.hwl@antgroup.com>
On Wed, 2026-01-14 at 21:21 +0800, Hou Wenlong wrote:
> When 'CONFIG_BROADCAST_TLB_FLUSH' is not enabled,
> mm_free_global_asid()
> remains a globally visible symbol and generates a useless function
> call
> to it in destroy_context(). Therefore, hide the mm_free_global_asid()
> definition under 'CONFIG_BROADCAST_TLB_FLUSH' and provide a static
> inline empty version when it is not enabled to remove the function
> call.
>
> Signed-off-by: Hou Wenlong <houwenlong.hwl@antgroup.com>
This may not create any measurable speedups, since it's
just one no-op function call in the exit path, but it
does reduce the size of the kernel on 32 bit systems where
CONFIG_BROADCAST_TLB_FLUSH is not enabled.
Reviewed-by: Rik van Riel <riel@surriel.com>
--
All Rights Reversed.
next prev parent reply other threads:[~2026-01-14 15:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 13:21 Hou Wenlong
2026-01-14 15:09 ` Rik van Riel [this message]
2026-01-14 19:28 ` Borislav Petkov
2026-01-15 3:28 ` Hou Wenlong
2026-01-15 3:38 ` [PATCH v2] " Hou Wenlong
2026-01-15 9:15 ` Borislav Petkov
2026-01-16 3:47 ` Hou Wenlong
2026-01-16 20:47 ` Borislav Petkov
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=733058ef2a54dc8323835fc26ca3b402ced5fc7f.camel@surriel.com \
--to=riel@surriel.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=houwenlong.hwl@antgroup.com \
--cc=hpa@zytor.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ryan.roberts@arm.com \
--cc=tglx@kernel.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®