From: Michael Ellerman <mpe@ellerman.id.au>
To: Luming Yu <luming.yu@shingroup.cn>
Cc: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
jialong.yang@shingroup.cn, luming.yu@gmail.com
Subject: Re: [RFC PATCH] powerpc/tlb: enable arch want batched unmap tlb flush
Date: Thu, 19 Sep 2024 22:52:21 +1000 [thread overview]
Message-ID: <87ldznreka.fsf@mail.lhotse> (raw)
In-Reply-To: <040533E1233A67C4+ZuugYFMsPMaDAjI9@HX09040029.powercore.com.cn>
Luming Yu <luming.yu@shingroup.cn> writes:
> On Thu, Sep 19, 2024 at 01:22:21PM +1000, Michael Ellerman wrote:
>> Luming Yu <luming.yu@shingroup.cn> writes:
>> > From: Yu Luming <luming.yu@gmail.com>
>> >
>> > ppc always do its own tracking for batch tlb.
>>
>> I don't think it does? :)
>>
>> I think you're referring to the batch handling in
>> arch/powerpc/include/asm/book3s/64/tlbflush-hash.h ?
>>
>> But that's only used for 64-bit Book3S with the HPT MMU.
>>
>> > By trivially enabling
>> > the ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH in ppc, ppc arch can re-use
>> > common code in rmap and reduce overhead and do optimization it could not
>> > have without a tlb flushing context at low architecture level.
>> >
>> > Signed-off-by: Luming Yu <luming.yu@shingroup.cn>
>> > ---
>> > arch/powerpc/Kconfig | 1 +
>> > arch/powerpc/include/asm/tlbbatch.h | 30 +++++++++++++++++++++++++++++
>> > 2 files changed, 31 insertions(+)
>> > create mode 100644 arch/powerpc/include/asm/tlbbatch.h
>>
>> This doesn't build:
>>
>> https://github.com/linuxppc/linux-snowpatch/actions/runs/10919442655
>>
>> Can you please follow the instructions here:
>>
>> https://github.com/linuxppc/wiki/wiki/Testing-with-GitHub-Actions
>>
>> Which describe how to fork our CI tree that has Github Actions
>> preconfigured, then you can apply your patches on top and push to github
>> and it will do some test builds for you. Notably it will do 32-bit
>> builds which is what broke here.
> thanks, I will take a look and do this for next patch before posting on mailing list. :-)
>
> Ideally it should also include qemu boot tests for targets that must work.
Those scripts do qemu boots of pseries p8/p9, powernv p8/p9, 44x,
e5500, g5, and mac99.
It doesn't boot full distros because that's too slow for Github Actions,
so it doesn't catch all bugs, but it's better than nothing.
> I think we could also need a powerpc yocto recipe as well to make
> patch test more customizable
> and reproducible than fedora/Debian distro. I've been searching for it
> for a while, but I couldn't find a useful one. Maybe I need to come up
> one of my own to facilitate the ci test bot ideas.
I've never used Yocto, not sure if it does/did support powerpc.
Buildroot can build powerpc images with lots of packages included.
cheers
next prev parent reply other threads:[~2024-09-19 12:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 9:25 [RFC PATCH] powerpc/tlb: enable arch want batched unmap tlb flush Luming Yu
2024-09-19 3:22 ` Michael Ellerman
2024-09-19 3:54 ` Luming Yu
2024-09-19 12:52 ` Michael Ellerman [this message]
2024-09-22 11:09 ` Ritesh Harjani
2024-09-23 2:57 ` Luming Yu
2024-09-23 5:18 ` Ritesh Harjani
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=87ldznreka.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=jialong.yang@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=luming.yu@gmail.com \
--cc=luming.yu@shingroup.cn \
--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