linux-kernel - Re: [RFC PATCH 0/6] Remove device private pages from physical address space

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <301376ee-3439-4d3e-a2c9-8604e7bf49fb@kernel.org>
Date: Fri, 28 Nov 2025 08:40:53 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Jordan Niethe <jniethe@...dia.com>, linux-mm@...ck.org
Cc: balbirs@...dia.com, matthew.brost@...el.com, akpm@...ux-foundation.org,
 linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
 ziy@...dia.com, apopple@...dia.com, lorenzo.stoakes@...cle.com,
 lyude@...hat.com, dakr@...nel.org, airlied@...il.com, simona@...ll.ch,
 rcampbell@...dia.com, mpenttil@...hat.com, jgg@...dia.com,
 willy@...radead.org
Subject: Re: [RFC PATCH 0/6] Remove device private pages from physical address
 space

On 11/28/25 05:41, Jordan Niethe wrote:
> Today, when creating these device private struct pages, the first step
> is to use request_free_mem_region() to get a range of physical address
> space large enough to represent the devices memory. This allocated
> physical address range is then remapped as device private memory using
> memremap_pages.

Just a note that as we are finishing the old release and are about to 
start the merge window (+ there is Thanksgiving), expect few replies to 
non-urgent stuff in the next weeks.

Having that said, the proposal is interesting. I recall that Alistair 
and Jason recently discussed removing the need of dealing with PFNs
completely for device-private.

Is that the result of these discussions?

-- 
Cheers

David