From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Dave Hansen <dave.hansen@intel.com>,
linux-mm@kvack.org, akpm@linux-foundation.org
Cc: Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Thomas Gleixner <tglx@linutronix.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
David Hildenbrand <david@redhat.com>,
Ryan Roberts <ryan.roberts@arm.com>,
x86@kernel.org, linux-riscv@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: Move set_pxd_safe() helpers from generic to platform
Date: Fri, 20 Sep 2024 12:12:47 +0530 [thread overview]
Message-ID: <925a26e2-bd53-4bf4-b22d-7a0e11581376@arm.com> (raw)
In-Reply-To: <3309e9ca-458b-4b10-8409-9fe315b60ae2@intel.com>
On 9/20/24 11:19, Dave Hansen wrote:
> On 9/19/24 22:30, Anshuman Khandual wrote:
>> set_pxd_safe() helpers that serve a specific purpose for both x86 and riscv
>> platforms, do not need to be in the common memory code. Otherwise they just
>> unnecessarily make the common API more complicated. This moves the helpers
>> from common code to platform instead.
>
> I just did a quick grep and don't see any difference between the _safe
> and normal variants. A quick grep didn't turn up any actual users.
>
> Did anyone actually double check that these are still needed on x86 in
> the first place?
arch/x86/mm/init_64.c
#define DEFINE_ENTRY(type1, type2, init) \
static inline void set_##type1##_init(type1##_t *arg1, \
type2##_t arg2, bool init) \
{ \
if (init) \
set_##type1##_safe(arg1, arg2); \
else \
set_##type1(arg1, arg2); \
}
DEFINE_ENTRY(p4d, p4d, init)
DEFINE_ENTRY(pud, pud, init)
DEFINE_ENTRY(pmd, pmd, init)
DEFINE_ENTRY(pte, pte, init)
We had triggered a build problem after dropping off set_pte_safe()
which seemed not to be used after normal grep.
https://lore.kernel.org/linux-mm/202409131220.CJ5MlGCG-lkp@intel.com/
next prev parent reply other threads:[~2024-09-20 6:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 5:30 Anshuman Khandual
2024-09-20 5:49 ` Dave Hansen
2024-09-20 6:42 ` Anshuman Khandual [this message]
2024-09-20 8:52 ` Dave Hansen
2024-09-20 9:27 ` Anshuman Khandual
2024-09-20 6:39 ` David Hildenbrand
2024-09-20 8:42 ` Anshuman Khandual
2024-09-24 5:28 ` Anshuman Khandual
2024-09-24 7:39 ` David Hildenbrand
2024-09-26 4:18 ` Anshuman Khandual
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=925a26e2-bd53-4bf4-b22d-7a0e11581376@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=ryan.roberts@arm.com \
--cc=tglx@linutronix.de \
--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