[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <71fade9d-be8f-40d1-b580-4fac89a16cc7@nvidia.com>
Date: Wed, 7 Jan 2026 17:08:43 -0800
From: John Hubbard <jhubbard@...dia.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Jordan Niethe <jniethe@...dia.com>
Cc: linux-mm@...ck.org, balbirs@...dia.com, matthew.brost@...el.com,
linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org,
david@...hat.com, 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
Subject: Re: [PATCH v2 00/11] Remove device private pages from physical
address space
On 1/7/26 12:06 PM, Andrew Morton wrote:
> On Wed, 7 Jan 2026 20:18:12 +1100 Jordan Niethe <jniethe@...dia.com> wrote:
...
> Can you better help us understand the seriousness of these problems?
> How much are our users really hurting from this?
>
A lot! We have been involved in escalations from various customers
who have attempted to enable, say, KASLR and HMM at the same time.
And they ran out of phys address space, forcing them into an awkward
ugly choice of one or the other, often.
This is a huge pain point and a barrier to HMM adoption.
thanks,
--
John Hubbard
Powered by blists - more mailing lists