From: Lorenzo Stoakes <lstoakes@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Hellstrom <thomas.hellstrom@linux.intel.com>,
Christian Konig <christian.koenig@amd.com>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jason Gunthorpe <jgg@ziepe.ca>,
Lorenzo Stoakes <lstoakes@gmail.com>
Subject: [PATCH 0/3] Remove drm/ttm-specific mm changes
Date: Sun, 12 Mar 2023 23:40:12 +0000 [thread overview]
Message-ID: <cover.1678661628.git.lstoakes@gmail.com> (raw)
Functionality was added specifically for the DRM TTM driver to support
mapping memory for VM_MIXEDMAP VMAs with customised protection flags,
however this has now been rolled back as issues were found with this
approach.
This series removes the mm changes too, retaining some of the useful
comments.
Lorenzo Stoakes (3):
mm: remove unused vmf_insert_mixed_prot()
mm: Remove vmf_insert_pfn_xxx_prot() for huge page-table entries
drm/ttm: Remove comment referencing now-removed
vmf_insert_mixed_prot()
drivers/gpu/drm/ttm/ttm_bo_vm.c | 2 +-
include/linux/huge_mm.h | 39 ++--------------------
include/linux/mm.h | 2 --
include/linux/mm_types.h | 7 +---
mm/huge_memory.c | 31 ++++++++----------
mm/memory.c | 57 +++++++++++----------------------
6 files changed, 35 insertions(+), 103 deletions(-)
--
2.39.2
next reply other threads:[~2023-03-12 23:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 23:40 Lorenzo Stoakes [this message]
2023-03-12 23:40 ` [PATCH 1/3] mm: remove unused vmf_insert_mixed_prot() Lorenzo Stoakes
2023-03-12 23:40 ` [PATCH 2/3] mm: Remove vmf_insert_pfn_xxx_prot() for huge page-table entries Lorenzo Stoakes
2023-03-12 23:40 ` [PATCH 3/3] drm/ttm: Remove comment referencing now-removed vmf_insert_mixed_prot() Lorenzo Stoakes
2023-03-13 7:47 ` Christian König
2023-03-13 19:38 ` 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=cover.1678661628.git.lstoakes@gmail.com \
--to=lstoakes@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=christian.koenig@amd.com \
--cc=dan.j.williams@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jgg@ziepe.ca \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=thomas.hellstrom@linux.intel.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