Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Alexandre Ghiti <alex@ghiti.fr>
Cc: Ryan Roberts <ryan.roberts@arm.com>,
	Alexandre Ghiti <alexghiti@rivosinc.com>,
	Will Deacon <will@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Mark Rutland <mark.rutland@arm.com>,
	Matthew Wilcox <willy@infradead.org>,
	Paul Walmsley <paul.walmsley@sifive.com>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
	linux-mm@kvack.org
Subject: Re: [PATCH v5 0/9] Merge arm64/riscv hugetlbfs contpte support
Date: Tue, 27 May 2025 10:37:47 +0100	[thread overview]
Message-ID: <a42e05b9-7568-4ebd-8797-c635c07d1884@lucifer.local> (raw)
In-Reply-To: <c5df4570-84a6-430a-ba49-81cf75930c16@ghiti.fr>

Andrew - does taking this proposed MAINTAINERS change through the riscv tree
work for you?

This series introduces the files being added there, so it seems sensible to add
the MAINTAINERS change to this series.

And I believe this series is intended to be taken through the riscv tree so
seems sensible to do it there?

Proposed entry is 'MEMORY MANAGEMENT - CONTPTE (CONTIGUOUS PTE SUPPORT)', which
is explicitly relevant for arm64, riscv.

Thanks!

On Tue, May 27, 2025 at 11:25:57AM +0200, Alexandre Ghiti wrote:
> Hi Lorenzo,
>
> On 5/21/25 16:57, Lorenzo Stoakes wrote:
[snip]
> > So right now it seems the files would consist of:
> >
> > include/linux/hugetlb_contpte.h
> > mm/hugetlb_contpte.c
> >
> > Is this correct?
>
>
> For now, it is, yes. When this first series gets merged, I would come up
> with another series that will introduce other files for riscv to support thp
> contpte based on the arm64 implementation.

Cool!

>
>
> >
> > Is this series intended to be taken by Andrew or through an arch tree?
>
>
> I can pick it up in the riscv tree once I have Acked-by from arm64
> maintainers.

Have pinged Andrew above on this, you'd need an acked-by from mm people also of
course.

But I guess what makes sense is to take this as a patch in the next respin of
this series that actually introduces this stuff.

So if Andrew took it, he'd have to take the whole series I would say.

>
>
> >
> > And who would you sensibly propose for M's and R's?
>
>
> Ryan is definitely a M, I would be happy to help as M too but if needed, a R
> is enough for me.

Ryan understands this area better than I do, so I would say it's up to him as to
whether he thinks this makes sense.

>
>
> >
> > If we are definitely adding things that sit outside hugetlb or anything
> > arch-specific, and is in fact generic mm code, then yes this should be a
> > section.
> >
> > Does contpte stand for 'Contiguous PTE'?
>
>
> Yes, that's the name arm64 gave to this feature (more understandable than
> svnapot for the riscv feature).

Cheers!

svnapot, guys... what? :P

>
>
> >
> > Then entry could perhaps be:
> >
> > MEMORY MANAGEMENT - CONTPTE (CONTIGUOUS PTE SUPPORT)
> >
> > I'd say this entry should probably be added as a patch in this series.
> >
> > If you give me a list of R's and M's and confirm those files I can very quickly
> > copy/pasta from an existing entry and then you could respin (and cc my work mail
> > for the series :P) and include that as an additional patch?
>
>
> You can do that or I can do it on my own based on your previous patches, as
> you prefer.

I absolutely prefer you to do the work haha! ;)

Please cc- me on the next respin with this change in and I can take a look.

>
>
> >
> > Happy to ACK that in that case.
>
>
> Thanks for jumping in!

No problem!

>
> Alex
>
>
> >
> >
> > > > [1] https://lore.kernel.org/linux-riscv/20240508191931.46060-1-alexghiti@rivosinc.com/
> > > >
> > > > Thanks,
> > > >
> > > > Alex
> > > >
> > > > > Will
> > Cheers, Lorenzo
> >

Cheers, Lorenzo


  reply	other threads:[~2025-05-27  9:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-21 13:06 [PATCH v5 0/9] Merge arm64/riscv hugetlbfs contpte support Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 1/9] riscv: Safely remove huge_pte_offset() when manipulating NAPOT ptes Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 2/9] riscv: Restore the pfn in a NAPOT pte when manipulated by core mm code Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 3/9] mm: Use common huge_ptep_get() function for riscv/arm64 Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 4/9] mm: Use common set_huge_pte_at() " Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 5/9] mm: Use common huge_pte_clear() " Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 6/9] mm: Use common huge_ptep_get_and_clear() " Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 7/9] mm: Use common huge_ptep_set_access_flags() " Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 8/9] mm: Use common huge_ptep_set_wrprotect() " Alexandre Ghiti
2025-03-21 13:06 ` [PATCH v5 9/9] mm: Use common huge_ptep_clear_flush() " Alexandre Ghiti
2025-03-21 17:24 ` [PATCH v5 0/9] Merge arm64/riscv hugetlbfs contpte support Christophe Leroy
2025-03-25 12:36   ` Alexandre Ghiti
2025-04-07 12:04 ` Alexandre Ghiti
2025-04-29 14:09   ` Ryan Roberts
2025-05-05 16:08     ` Alexandre Ghiti
2025-05-08 12:30       ` Will Deacon
2025-05-09 11:09         ` Alexandre Ghiti
2025-05-09 13:02           ` Ryan Roberts
2025-05-21 14:57             ` Lorenzo Stoakes
2025-05-27  9:25               ` Alexandre Ghiti
2025-05-27  9:37                 ` Lorenzo Stoakes [this message]
2025-05-28 14:51                   ` Ryan Roberts

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=a42e05b9-7568-4ebd-8797-c635c07d1884@lucifer.local \
    --to=lorenzo.stoakes@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=alexghiti@rivosinc.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=mark.rutland@arm.com \
    --cc=palmer@dabbelt.com \
    --cc=paul.walmsley@sifive.com \
    --cc=ryan.roberts@arm.com \
    --cc=will@kernel.org \
    --cc=willy@infradead.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