linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "Alice Ryhl" <aliceryhl@google.com>,
	"kernel test robot" <lkp@intel.com>,
	"Liam R. Howlett" <Liam.Howlett@oracle.com>,
	"Miguel Ojeda" <ojeda@kernel.org>,
	"Matthew Wilcox" <willy@infradead.org>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	"John Hubbard" <jhubbard@nvidia.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Arnd Bergmann" <arnd@arndb.de>, "Jann Horn" <jannh@google.com>,
	"Suren Baghdasaryan" <surenb@google.com>,
	oe-kbuild-all@lists.linux.dev,
	"Linux Memory Management List" <linux-mm@kvack.org>,
	"Alex Gaynor" <alex.gaynor@gmail.com>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Gary Guo" <gary@garyguo.net>,
	"Björn Roy Baron" <bjorn3_gh@protonmail.com>,
	"Benno Lossin" <benno.lossin@proton.me>,
	"Andreas Hindborg" <a.hindborg@kernel.org>,
	"Trevor Gross" <tmgross@umich.edu>,
	linux-kernel@vger.kernel.org, rust-for-linux@vger.kernel.org
Subject: Re: [PATCH v15 5/9] mm: rust: add mmput_async support
Date: Mon, 10 Mar 2025 15:45:01 +0100	[thread overview]
Message-ID: <CANiq72kAY8hfN_RW-=h-gmFQbq=0DDSQ=ZQr+M3KhJgnsW6n5Q@mail.gmail.com> (raw)
In-Reply-To: <f8da228a-fbc9-413c-8fbe-cfbf074a3053@lucifer.local>

On Mon, Mar 10, 2025 at 3:20 PM Lorenzo Stoakes
<lorenzo.stoakes@oracle.com> wrote:
>
> Yeah, !CONFIG_MMU is a constant source of headaches and pain :/ is there a
> way to just require CONFIG_MMU for the rust bits? As far as I'm concerned
> !CONFIG_MMU is a relic... (not everybody agrees of course :>)

I guess you could simply limit `CONFIG_RUST` to it, but yeah, I guess
it depends on how many people you estimate would like to mix both, and
the bandwidth/patience available to support it.

Cheers,
Miguel


  reply	other threads:[~2025-03-10 14:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-04 11:49 [PATCH v15 0/9] Rust support for mm_struct, vm_area_struct, and mmap Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 1/9] mm: rust: add abstraction for struct mm_struct Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 2/9] mm: rust: add vm_area_struct methods that require read access Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 3/9] mm: rust: add vm_insert_page Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 4/9] mm: rust: add lock_vma_under_rcu Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 5/9] mm: rust: add mmput_async support Alice Ryhl
2025-03-09 11:37   ` kernel test robot
2025-03-10  9:23     ` Alice Ryhl
2025-03-10 14:19       ` Lorenzo Stoakes
2025-03-10 14:45         ` Miguel Ojeda [this message]
2025-03-04 11:49 ` [PATCH v15 6/9] mm: rust: add VmaNew for f_ops->mmap() Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 7/9] rust: miscdevice: add mmap support Alice Ryhl
2025-03-04 11:49 ` [PATCH v15 8/9] task: rust: rework how current is accessed Alice Ryhl
2025-03-04 11:50 ` [PATCH v15 9/9] mm: rust: add MEMORY MANAGEMENT [RUST] Alice Ryhl
2025-03-04 11:54   ` Lorenzo Stoakes
2025-03-04 14:50   ` Liam R. Howlett

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='CANiq72kAY8hfN_RW-=h-gmFQbq=0DDSQ=ZQr+M3KhJgnsW6n5Q@mail.gmail.com' \
    --to=miguel.ojeda.sandonis@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=a.hindborg@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex.gaynor@gmail.com \
    --cc=aliceryhl@google.com \
    --cc=arnd@arndb.de \
    --cc=benno.lossin@proton.me \
    --cc=bjorn3_gh@protonmail.com \
    --cc=boqun.feng@gmail.com \
    --cc=gary@garyguo.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=jhubbard@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=ojeda@kernel.org \
    --cc=rust-for-linux@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=tmgross@umich.edu \
    --cc=vbabka@suse.cz \
    --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