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 [thread overview]
Message-ID: <20240523223745.395337-1-peterx@redhat.com> (raw)
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
next reply other threads:[~2024-05-23 22:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-23 22:37 Peter Xu [this message]
2024-05-23 22:37 ` [PATCH RFC 1/2] mm/x86/pat: Only untrack the pfn range if unmap region Peter Xu
2024-05-23 22:37 ` [PATCH RFC 2/2] mm/x86/pat: Do proper PAT bit shift for large mappings Peter Xu
2024-05-23 22:48 ` Dave Hansen
2024-05-23 23:07 ` Peter Xu
2024-05-24 0:53 ` Peter Xu
2024-05-24 3:30 ` Dave Hansen
2024-05-24 23:55 ` Peter Xu
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=20240523223745.395337-1-peterx@redhat.com \
--to=peterx@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alex.williamson@redhat.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=jgg@nvidia.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=x86@kernel.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.