From: Michael Ellerman <mpe@ellerman.id.au>
To: "Aneesh Kumar K.V" <aneesh.kumar@kernel.org>,
Kunwu Chan <chentao@kylinos.cn>,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
naveen.n.rao@linux.ibm.com
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc/mm: Code cleanup for __hash_page_thp
Date: Thu, 29 Feb 2024 17:18:32 +1100 [thread overview]
Message-ID: <87wmqng5dz.fsf@mail.lhotse> (raw)
In-Reply-To: <87bk80kjup.fsf@kernel.org>
Aneesh Kumar K.V <aneesh.kumar@kernel.org> writes:
> Michael Ellerman <mpe@ellerman.id.au> writes:
>> Kunwu Chan <chentao@kylinos.cn> writes:
>>> On 2024/2/26 18:49, Michael Ellerman wrote:
>>>> Kunwu Chan <chentao@kylinos.cn> writes:
>>>>> This part was commented from commit 6d492ecc6489
>>>>> ("powerpc/THP: Add code to handle HPTE faults for hugepages")
>>>>> in about 11 years before.
>>>>>
>>>>> If there are no plans to enable this part code in the future,
>>>>> we can remove this dead code.
>>>>
>>>> I agree the code can go. But I'd like it to be replaced with a comment
>>>> explaining what the dead code was trying to say.
>>
>>> Thanks, i'll update a new patch with the following comment:
>>> /*
>>> * No CPU has hugepages but lacks no execute, so we
>>> * don't need to worry about cpu no CPU_FTR_COHERENT_ICACHE feature case
>>> */
>>
>> Maybe wait until we can get some input from Aneesh. I'm not sure the
>> code/comment are really up to date.
>
> How about?
>
> modified arch/powerpc/mm/book3s64/hash_hugepage.c
> @@ -58,17 +58,13 @@ int __hash_page_thp(unsigned long ea, unsigned long access, unsigned long vsid,
> return 0;
>
> rflags = htab_convert_pte_flags(new_pmd, flags);
> + /*
> + * THPs are only supported on platforms that can do mixed page size
> + * segments (MPSS) and all such platforms have coherent icache. Hence we
> + * don't need to do lazy icache flush (hash_page_do_lazy_icache()) on
> + * noexecute fault.
> + */
Yeah thanks that looks good.
It could say "see eg. __hash_page_4K()", but that's probably unnecessary
as it mentions hash_page_do_lazy_icache(), and anyone interested is just
going to grep for that anyway.
cheers
next prev parent reply other threads:[~2024-02-29 6:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 9:26 [PATCH] powerpc/mm: Code cleanup for __hash_page_thp Kunwu Chan
2024-02-26 10:49 ` Michael Ellerman
2024-02-27 3:14 ` Kunwu Chan
2024-02-27 6:07 ` Michael Ellerman
2024-02-27 9:32 ` Kunwu Chan
2024-02-29 3:52 ` Aneesh Kumar K.V
2024-02-29 6:18 ` Michael Ellerman [this message]
2024-02-29 9:28 ` Kunwu Chan
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=87wmqng5dz.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@kernel.org \
--cc=chentao@kylinos.cn \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).