[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <111407dd-3628-4cbc-91ea-a1c31e27ed2b@intel.com>
Date: Wed, 4 Sep 2024 14:29:47 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: "Liam R. Howlett" <Liam.Howlett@...cle.com>,
Nam Cao <namcao@...utronix.de>, Dave Hansen <dave.hansen@...ux.intel.com>,
Andy Lutomirski <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
Borislav Petkov <bp@...en8.de>, x86@...nel.org,
"H. Peter Anvin" <hpa@...or.com>, Andrew Morton <akpm@...ux-foundation.org>,
Vlastimil Babka <vbabka@...e.cz>,
Lorenzo Stoakes <lorenzo.stoakes@...cle.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, bigeasy@...utronix.de
Subject: Re: [PATCH] x86/mm/pat: Support splitting of virtual memory areas
On 9/4/24 11:40, Liam R. Howlett wrote:
> But those ranges won't exist. What appears to be happening in this code
> is that there are higher levels of non-overlapping ranges with
> memory (cache) types (or none are defined) , which are tracked on page
> granularity. So we can't have a page that has two memory type.
Yeah, that's the key. Each page should be uniquely covered by one and
only one tree leaf.
Nam, I didn't see your original patch in my inbox and I don't see it on
lore either. Is there something funky going on there?
Powered by blists - more mailing lists