All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Lain Fearyncess Yang <fearyncess@aosc.io>,
	WANG Xuerui <kernel@xen0n.name>,
	Kexy Biscuit <kexybiscuit@aosc.io>,
	Mingcong Bai <jeffbai@aosc.io>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, Arnd Bergmann <arnd@arndb.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] loongarch: wire up memfd_secret system call
Date: Sun, 25 Jan 2026 11:58:58 +0200	[thread overview]
Message-ID: <aXXpYqDyTeftKV2c@kernel.org> (raw)
In-Reply-To: <CAAhV-H5tHZRHmXSA6m+fyhaN9nNjLFbEiVK7OWjL8EoJn16doQ@mail.gmail.com>

On Sun, Jan 25, 2026 at 12:03:25PM +0800, Huacai Chen wrote:
> On Fri, Jan 9, 2026 at 4:21 PM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Fri, Jan 09, 2026 at 01:10:51PM +0800, Lain Fearyncess Yang wrote:
> > > From: "Lain \"Fearyncess\" Yang" <fearyncess@aosc.io>
> > >
> > > LoongArch supports ARCH_HAS_SET_DIRECT_MAP, therefore wire up the
> > > memfd_secret system call, which depends on it.
> >
> > LoongArch version of set_memory* does not support splitting of leaf PMD
> > entries. Does LoongArch always use PTE-level mappings in the direct map?
> No PMD level mappings now.

Thanks for the clarification. You can add

Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>

if it's not too late :)

> Huacai

-- 
Sincerely yours,
Mike.

WARNING: multiple messages have this Message-ID (diff)
From: Mike Rapoport <rppt@kernel.org>
To: Huacai Chen <chenhuacai@kernel.org>
Cc: Lain Fearyncess Yang <fearyncess@aosc.io>,
	WANG Xuerui <kernel@xen0n.name>,
	Kexy Biscuit <kexybiscuit@aosc.io>,
	Mingcong Bai <jeffbai@aosc.io>,
	Andrew Morton <akpm@linux-foundation.org>,
	David Hildenbrand <david@kernel.org>,
	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Suren Baghdasaryan <surenb@google.com>,
	Michal Hocko <mhocko@suse.com>, Shuah Khan <shuah@kernel.org>,
	Paul Walmsley <pjw@kernel.org>,
	Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	Alexandre Ghiti <alex@ghiti.fr>, Arnd Bergmann <arnd@arndb.de>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	loongarch@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-riscv@lists.infradead.org
Subject: Re: [PATCH] loongarch: wire up memfd_secret system call
Date: Sun, 25 Jan 2026 11:58:58 +0200	[thread overview]
Message-ID: <aXXpYqDyTeftKV2c@kernel.org> (raw)
In-Reply-To: <CAAhV-H5tHZRHmXSA6m+fyhaN9nNjLFbEiVK7OWjL8EoJn16doQ@mail.gmail.com>

On Sun, Jan 25, 2026 at 12:03:25PM +0800, Huacai Chen wrote:
> On Fri, Jan 9, 2026 at 4:21 PM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > On Fri, Jan 09, 2026 at 01:10:51PM +0800, Lain Fearyncess Yang wrote:
> > > From: "Lain \"Fearyncess\" Yang" <fearyncess@aosc.io>
> > >
> > > LoongArch supports ARCH_HAS_SET_DIRECT_MAP, therefore wire up the
> > > memfd_secret system call, which depends on it.
> >
> > LoongArch version of set_memory* does not support splitting of leaf PMD
> > entries. Does LoongArch always use PTE-level mappings in the direct map?
> No PMD level mappings now.

Thanks for the clarification. You can add

Acked-by: Mike Rapoport (Microsoft) <rppt@kernel.org>

if it's not too late :)

> Huacai

-- 
Sincerely yours,
Mike.

_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv

  reply	other threads:[~2026-01-25  9:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  5:10 [PATCH] loongarch: wire up memfd_secret system call Lain Fearyncess Yang
2026-01-09  5:10 ` Lain Fearyncess Yang
2026-01-09  6:45 ` Arnd Bergmann
2026-01-09  6:45   ` Arnd Bergmann
2026-01-09  8:21 ` Mike Rapoport
2026-01-09  8:21   ` Mike Rapoport
2026-01-25  4:03   ` Huacai Chen
2026-01-25  4:03     ` Huacai Chen
2026-01-25  9:58     ` Mike Rapoport [this message]
2026-01-25  9:58       ` Mike Rapoport
2026-01-09 13:28 ` David Hildenbrand (Red Hat)
2026-01-09 13:28   ` David Hildenbrand (Red Hat)
2026-01-25  4:03 ` Huacai Chen
2026-01-25  4:03   ` Huacai Chen

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=aXXpYqDyTeftKV2c@kernel.org \
    --to=rppt@kernel.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=arnd@arndb.de \
    --cc=chenhuacai@kernel.org \
    --cc=david@kernel.org \
    --cc=fearyncess@aosc.io \
    --cc=jeffbai@aosc.io \
    --cc=jiaxun.yang@flygoat.com \
    --cc=kernel@xen0n.name \
    --cc=kexybiscuit@aosc.io \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=loongarch@lists.linux.dev \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=mhocko@suse.com \
    --cc=palmer@dabbelt.com \
    --cc=pjw@kernel.org \
    --cc=shuah@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.