From: Lorenzo Stoakes <ljs@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jason Gunthorpe <jgg@ziepe.ca>, Peter Xu <peterx@redhat.com>,
Alex Williamson <alex@shazbot.org>,
Anthony Pighin <anthony.pighin@nokia.com>,
linux-kernel@vger.kernel.org,
Kefeng Wang <wangkefeng.wang@huawei.com>,
kvm@vger.kernel.org, linux-mm@kvack.org,
"Liam R. Howlett" <liam@infradead.org>,
Ryan Roberts <ryan.roberts@arm.com>
Subject: Re: [PATCH] vfio: Request THP-aligned mmap for device fds
Date: Mon, 22 Jun 2026 16:44:18 +0100 [thread overview]
Message-ID: <ajlX9BH4E4JncZqs@lucifer> (raw)
In-Reply-To: <ajVqRiAMG23QGseC@casper.infradead.org>
On Fri, Jun 19, 2026 at 05:11:50PM +0100, Matthew Wilcox wrote:
> On Thu, Jun 18, 2026 at 12:28:05PM -0300, Jason Gunthorpe wrote:
> > On Thu, Jun 18, 2026 at 03:55:58PM +0100, Lorenzo Stoakes wrote:
> > > Can't we figure this out from what the driver tells us when it invokes an
> > > mmap_prepare action?
> >
> > VFIO installs the pages via fault handler so there is not a naturally
> > existing way to pass in the pfn?
>
> Is there an advantage to doing it this way? I understand why we (eg)
> demand-page pagecache, that's obvious. But I've never really understood
> the advantage to taking page faults for PFNMAP areas where we don't
> really do anything, just figure out which PFN needs to be installed.
> It defers page table allocation, I suppose.
>
> > > Not in favour of that, fear it'll be seen as a new go-faster stripe. Ask
> > > somebody how many free pints they want and they may veer rather towards the
> > > upper bound :)
> >
> > I think you need something, otherwise we will be aligning VMAs that
> > never have anything larger than a 2M THP to 1GB boundaries, doesn't
> > seem good.
>
> If Lorenzo's willing to move the mmap_prepare call earlier, to before we
> allocate the vma then we can do it that way ...
Hmm, I wonder if we could defer the get_unmapped_area stuff until later.
Taking a quick look it's actually not totally insane to do that... Let me fiddle
around with it...
Thanks, Lorenzo
next prev parent reply other threads:[~2026-06-22 15:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260616180129.160016-1-anthony.pighin@nokia.com>
[not found] ` <20260616163054.77fdb61a@shazbot.org>
[not found] ` <ajKtdCN0AlbmBnAj@x1.local>
2026-06-17 18:34 ` [PATCH] vfio: Request THP-aligned mmap for device fds Matthew Wilcox
2026-06-17 19:29 ` Jason Gunthorpe
2026-06-18 14:55 ` Lorenzo Stoakes
2026-06-18 15:04 ` Matthew Wilcox
2026-06-18 15:30 ` Jason Gunthorpe
2026-06-18 15:56 ` Lorenzo Stoakes
2026-06-19 13:16 ` Jason Gunthorpe
2026-06-22 16:54 ` Lorenzo Stoakes
2026-06-18 15:28 ` Jason Gunthorpe
2026-06-19 16:11 ` Matthew Wilcox
2026-06-19 17:07 ` Jason Gunthorpe
2026-06-22 15:42 ` Lorenzo Stoakes
2026-06-22 15:44 ` Lorenzo Stoakes [this message]
2026-06-19 15:04 ` Ryan Roberts
2026-06-22 15:48 ` Lorenzo Stoakes
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=ajlX9BH4E4JncZqs@lucifer \
--to=ljs@kernel.org \
--cc=alex@shazbot.org \
--cc=anthony.pighin@nokia.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=wangkefeng.wang@huawei.com \
--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