[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9c8a139e-9e20-4f39-b750-fa390a8a745a@intel.com>
Date: Tue, 2 Jul 2024 11:38:53 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Andrew Morton <akpm@...ux-foundation.org>,
Yosry Ahmed <yosryahmed@...gle.com>
Cc: x86@...nel.org, Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>,
Dave Hansen <dave.hansen@...ux.intel.com>, "H. Peter Anvin" <hpa@...or.com>,
Andy Lutomirski <luto@...nel.org>, Peter Zijlstra <peterz@...radead.org>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@...el.com>, linux-mm@...ck.org,
linux-kernel@...r.kernel.org
Subject: Re: [RESEND PATCH v3 0/3] x86/mm: LAM fixups and cleanups
On 7/2/24 11:35, Andrew Morton wrote:
> But when people run older (or current) kernels on newer hardware, they
> will hit this. So a backport to cover 82721d8b25d7 ("x86/mm: Handle
> LAM on context switch") is needed.
>
> The series doesn't seem to be getting much traction so I can add it to
> mm.git's mm-unstable branch for wider testing, but it's clearly an x86
> tree thing.
I was really hoping Andy L would look at this since he suggested this
whole thing really.
I completely agree that this needs some wider testing. How about I pull
it into x86/mm so it gets some linux-next testing instead of having it
in mm-unstable? Maybe it'll also attract Andy's attention once it's in
there.
Powered by blists - more mailing lists