Received-SPF: pass (google.com: domain of linux-kernel+bounces-188079-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
From: Peter Xu <peterx@redhat.com>
To: linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Jason Gunthorpe <jgg@nvidia.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	Dave Hansen <dave.hansen@linux.intel.com>,
	Andy Lutomirski <luto@kernel.org>,
	Matthew Wilcox <willy@infradead.org>,
	peterx@redhat.com,
	Dan Williams <dan.j.williams@intel.com>,
	"Kirill A . Shutemov" <kirill@shutemov.name>,
	Mike Rapoport <rppt@kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Michal Hocko <mhocko@suse.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Suren Baghdasaryan <surenb@google.com>,
	Borislav Petkov <bp@alien8.de>,
	x86@kernel.org
Subject: [PATCH RFC 0/2] mm/x86/pat: Fix two possible issues
Date: Thu, 23 May 2024 18:37:43 -0400
Message-ID: <20240523223745.395337-1-peterx@redhat.com>
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit

I'm recently looking at the possibility of mapping PCIe large bars to use
huge mappings (just like thp or hugetlb).  Then I noticed these only when
reading the code.

I don't think I'm familiar enough with the whole PAT system, however I
figured I should post them out to collect some comments, hencing marking
this small series as RFC.

Please feel free to have a look at each of them; I've put more words in the
commit message than here, as the two issues are not related.  Any comments
are welcomed.

Thanks,

Peter Xu (2):
  mm/x86/pat: Only untrack the pfn range if unmap region
  mm/x86/pat: Do proper PAT bit shift for large mappings

 mm/huge_memory.c | 4 ++--
 mm/memory.c      | 5 ++---
 2 files changed, 4 insertions(+), 5 deletions(-)

-- 
2.45.0