From: Dave Hansen <dave.hansen@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Yosry Ahmed <yosryahmed@google.com>
Cc: x86@kernel.org, Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [RESEND PATCH v3 0/3] x86/mm: LAM fixups and cleanups
Date: Tue, 2 Jul 2024 11:38:53 -0700 [thread overview]
Message-ID: <9c8a139e-9e20-4f39-b750-fa390a8a745a@intel.com> (raw)
In-Reply-To: <20240702113554.2471f000055f3c717fced4f5@linux-foundation.org>
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.
next prev parent reply other threads:[~2024-07-02 18:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-02 13:21 Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 1/3] x86/mm: Use IPIs to synchronize LAM enablement Yosry Ahmed
2024-07-02 18:58 ` Borislav Petkov
2024-07-02 19:00 ` Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 2/3] x86/mm: Fix LAM inconsistency during context switch Yosry Ahmed
2024-07-02 13:21 ` [RESEND PATCH v3 3/3] x86/mm: Cleanup prctl_enable_tagged_addr() nr_bits error checking Yosry Ahmed
2024-07-02 17:36 ` [RESEND PATCH v3 0/3] x86/mm: LAM fixups and cleanups Andrew Morton
2024-07-02 17:39 ` Yosry Ahmed
2024-07-02 18:35 ` Andrew Morton
2024-07-02 18:38 ` Dave Hansen [this message]
2024-07-02 18:55 ` Yosry Ahmed
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=9c8a139e-9e20-4f39-b750-fa390a8a745a@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=yosryahmed@google.com \
/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