From: Andrew Morton <akpm@linux-foundation.org>
To: John Hubbard <jhubbard@nvidia.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
alex.sierra@amd.com, willy@infradead.org, hch@lst.de,
Felix.Kuehling@amd.com, apopple@nvidia.com, david@redhat.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] mm: re-allow pinning of zero pfns (again)
Date: Sat, 27 Aug 2022 18:40:21 -0700 [thread overview]
Message-ID: <20220827184021.4e100b9eda3a9141217ec60d@linux-foundation.org> (raw)
In-Reply-To: <033c2e8d-8ba9-3e0b-9dee-7d0973c708fa@nvidia.com>
On Sat, 27 Aug 2022 17:59:32 -0700 John Hubbard <jhubbard@nvidia.com> wrote:
>
> /* The zero page is always allowed to be pinned. */
Wow, that's really verbose :)
--- a/include/linux/mm.h~mm-re-allow-pinning-of-zero-pfns-again-fix
+++ a/include/linux/mm.h
@@ -1544,11 +1544,7 @@ static inline bool is_longterm_pinnable_
if (mt == MIGRATE_CMA || mt == MIGRATE_ISOLATE)
return false;
#endif
- /*
- * The zero page might reside in a movable zone, however it may not
- * be migrated and can therefore be pinned. The vfio subsystem pins
- * user mappings including the zero page for IOMMU translation.
- */
+ /* The zero page may always be pinned */
if (is_zero_pfn(page_to_pfn(page)))
return true;
_
next prev parent reply other threads:[~2022-08-28 1:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 16:53 [PATCH v2] mm: re-allow pinning of zero pfns (again) Alex Williamson
2022-08-26 19:01 ` Laba, SlawomirX
2022-08-28 0:59 ` John Hubbard
2022-08-28 1:40 ` Andrew Morton [this message]
2022-08-28 12:37 ` Alex Williamson
2022-08-28 17:16 ` John Hubbard
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=20220827184021.4e100b9eda3a9141217ec60d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Felix.Kuehling@amd.com \
--cc=alex.sierra@amd.com \
--cc=alex.williamson@redhat.com \
--cc=apopple@nvidia.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.