From: Dave Hansen <dave.hansen@intel.com>
To: Nam Cao <namcao@linutronix.de>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
bigeasy@linutronix.de
Subject: Re: [PATCH] x86/mm/pat: Support splitting of virtual memory areas
Date: Thu, 5 Sep 2024 13:52:40 -0700 [thread overview]
Message-ID: <5bcc86bd-d94d-4f4a-8f4e-81fad78c3e21@intel.com> (raw)
In-Reply-To: <20240905200802.2vY0SstV@linutronix.de>
On 9/5/24 13:08, Nam Cao wrote:
>
> If I pause this program right after the two mmap(), before any munmap(),
> then:
> $cat /sys/kernel/debug/x86/pat_memtype_list
> PAT memtype list:
> PAT: [mem 0x00000000bffe0000-0x00000000bffe2000] write-back
> PAT: [mem 0x00000000bffe1000-0x00000000bffe2000] write-back
> PAT: [mem 0x00000000fd000000-0x00000000fd002000] uncached-minus <-- what I described
> PAT: [mem 0x00000000fd001000-0x00000000fd003000] uncached-minus <-- what I described
> PAT: [mem 0x00000000febc0000-0x00000000febe0000] uncached-minus
Well, that's not what I had in mind, so I'm obviously the confused one.
Let me take a look through your example and see if I can offer any
alternatives.
prev parent reply other threads:[~2024-09-05 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240825152403.3171682-1-namcao@linutronix.de>
2024-08-25 16:04 ` Lorenzo Stoakes
2024-08-26 7:11 ` Nam Cao
2024-08-26 13:58 ` Liam R. Howlett
2024-08-27 7:58 ` Nam Cao
2024-08-27 16:01 ` Liam R. Howlett
2024-09-03 10:36 ` Nam Cao
2024-09-03 15:56 ` Liam R. Howlett
2024-09-04 7:59 ` Nam Cao
2024-09-04 18:40 ` Liam R. Howlett
2024-09-04 21:29 ` Dave Hansen
2024-09-05 20:09 ` Nam Cao
2024-09-05 20:08 ` Nam Cao
2024-09-05 20:52 ` Dave Hansen [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=5bcc86bd-d94d-4f4a-8f4e-81fad78c3e21@intel.com \
--to=dave.hansen@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=namcao@linutronix.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vbabka@suse.cz \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox