linux-kernel - Re: [PATCH v6 00/13] 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] [day] [month] [year] [list]

Message-ID: <ef673543-b03b-47b3-bd40-2540a56b6333@kernel.org>
Date: Fri, 6 Feb 2026 14:08:42 +0100
From: "David Hildenbrand (Arm)" <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, linuxppc-dev@...ts.ozlabs.org,
 intel-xe@...ts.freedesktop.org, jgg@...pe.ca, Felix.Kuehling@....com,
 jhubbard@...dia.com, maddy@...ux.ibm.com, mpe@...erman.id.au,
 ying.huang@...ux.alibaba.com
Subject: Re: [PATCH v6 00/13] Remove device private pages from physical
 address space

> By removing the device private pages from the physical address space,
> this series also opens up the possibility to moving away from tracking
> device private memory using struct pages in the future. This is
> desirable as on systems with large amounts of memory these device
> private struct pages use a signifiant amount of memory and take a
> significant amount of time to initialize.
> 
> Changes in v6
> -------------
> - Fix maybe unused in kgd2kfd_init_zone_device()
> - Replace division by PAGE_SIZE with DIV_ROUND_UP() when setting
> nr_pages. This mirrors the align up that previously happened in
> get_free_mem_region()
> 
> Note removed previous discussion in the cover letter relating to aarch64
> and memremap_pages() as this was actually already addressed in commit
> eeb8fdfcf090 ("arm64: Expose the end of the linear map in PHYSMEM_END").
> 

Now that I stumbled over v6, same comment; planning on taking a look soon.

-- 
Cheers,

David