From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Balbir Singh <balbirs@nvidia.com>, Alistair Popple <apopple@nvidia.com>
Cc: Zi Yan <ziy@nvidia.com>, John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Peter Xu <peterx@redhat.com>,
Mike Rapoport <rppt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, Sourab Gupta <sougupta@nvidia.com>
Subject: Re: [PATCH] mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios
Date: Thu, 11 Jun 2026 09:35:19 +0200 [thread overview]
Message-ID: <07fa0325-25f9-4179-bcfa-fbef8938c40a@kernel.org> (raw)
In-Reply-To: <aioG_ko6HoOv8qlc@parvat>
On 6/11/26 03:12, Balbir Singh wrote:
> On Thu, Jun 11, 2026 at 10:49:59AM +1000, Alistair Popple wrote:
>> On 2026-06-06 at 02:20 +1000, Zi Yan <ziy@nvidia.com> wrote...
>>>
>>>
>>> Right, I will work on my solution soon. Meanwhile, this change
>>> is simpler and can be easily back ported.
>>
>> Thanks.
>>
>>> BTW, should it be back ported to older kernels?
>>
>> Yes to any with f002882ca369 ("mm: merge folio_is_secretmem() and
>> folio_fast_pin_allowed() into gup_fast_folio_allowed()") - we have got bug
>> reports as a result of the lowered perf that commit causes.
>>
>> - Alistair
>>
>
> Ping @akpm to pick this up, if there is no objection @david
Fine with me
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
--
Cheers,
David
prev parent reply other threads:[~2026-06-11 7:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 1:46 [PATCH] mm/gup: fix GUP-fast fallback for NULL-mapping order-0 folios John Hubbard
2026-04-09 2:07 ` Andrew Morton
2026-04-09 2:09 ` John Hubbard
2026-04-09 7:52 ` David Hildenbrand (Arm)
2026-04-09 15:05 ` Zi Yan
2026-04-09 15:11 ` David Hildenbrand (Arm)
2026-04-09 16:55 ` Zi Yan
2026-04-09 17:31 ` David Hildenbrand (Arm)
2026-04-09 17:33 ` Zi Yan
2026-05-15 0:09 ` Balbir Singh
2026-05-18 9:42 ` David Hildenbrand (Arm)
2026-06-05 5:17 ` Alistair Popple
2026-06-05 9:22 ` David Hildenbrand (Arm)
2026-06-05 16:20 ` Zi Yan
2026-06-11 0:49 ` Alistair Popple
2026-06-11 1:12 ` Balbir Singh
2026-06-11 7:35 ` David Hildenbrand (Arm) [this message]
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=07fa0325-25f9-4179-bcfa-fbef8938c40a@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=apopple@nvidia.com \
--cc=balbirs@nvidia.com \
--cc=jgg@ziepe.ca \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.com \
--cc=rppt@kernel.org \
--cc=sougupta@nvidia.com \
--cc=ziy@nvidia.com \
/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