From: Sasha Levin <sashal@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Erwan Velu <erwanaliasr1@gmail.com>,
linux-kernel@vger.kernel.org, stable@vger.kernel.org,
tglx@linutronix.de, mingo@redhat.com,
dave.hansen@linux.intel.com, x86@kernel.org, puwen@hygon.cn,
seanjc@google.com, kim.phillips@amd.com, jmattson@google.com,
babu.moger@amd.com, peterz@infradead.org,
rick.p.edgecombe@intel.com, brgerst@gmail.com,
ashok.raj@intel.com, mjguzik@gmail.com, jpoimboe@kernel.org,
nik.borisov@suse.com, aik@amd.com, vegard.nossum@oracle.com,
daniel.sneddon@linux.intel.com, acdunlap@google.com,
pavel@denx.de
Subject: Re: [PATCH AUTOSEL 5.15 11/12] x86/barrier: Do not serialize MSR accesses on AMD
Date: Fri, 29 Nov 2024 10:37:06 -0500 [thread overview]
Message-ID: <Z0nfomc6TKd-17S9@sashalap> (raw)
In-Reply-To: <20241129133310.GDZ0nClg7mDbFaqxft@fat_crate.local>
On Fri, Nov 29, 2024 at 02:33:10PM +0100, Borislav Petkov wrote:
>On Fri, Nov 29, 2024 at 10:30:11AM +0100, Erwan Velu wrote:
>> We all know how difficult it is to maintain kernels and support the hard
>> work you do on this. It's also up to us, the users & industry, to give
>> feedback and testing around this type of story. It could probably be
>> interesting to have a presentation around this at KernelRecipes ;)
Or LPC? I don't usually end up attending KR but Greg is always there :)
>Yes, absolutely.
>
>And you should reserve a whole slot of 1h after it for discussion. Because all
>the folks using stable kernels or doing backports will definitely have
>experience and thoughts to share... who knows, might improve the proces in the
>end.
If there are enough folks who are interested in a BoF session I'm happy
to help set it up for LPC.
--
Thanks,
Sasha
next prev parent reply other threads:[~2024-11-29 15:37 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 23:26 [PATCH AUTOSEL 5.15 01/12] watch_queue: fix kcalloc() arguments order Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 02/12] powerpc/mm: Fix null-pointer dereference in pgtable_cache_add Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 03/12] arm64: irq: set the correct node for VMAP stack Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 04/12] drivers/perf: pmuv3: don't expose SW_INCR event in sysfs Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 05/12] powerpc: Fix build error due to is_valid_bugaddr() Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 06/12] powerpc/mm: Fix build failures due to arch_reserved_kernel_pages() Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 07/12] powerpc/64s: Fix CONFIG_NUMA=n build due to create_section_mapping() Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 08/12] x86/boot: Ignore NMIs during very early boot Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 09/12] powerpc: pmd_move_must_withdraw() is only needed for CONFIG_TRANSPARENT_HUGEPAGE Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 10/12] powerpc/lib: Validate size for vector operations Sasha Levin
2024-01-15 23:26 ` Sasha Levin
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 11/12] x86/barrier: Do not serialize MSR accesses on AMD Sasha Levin
2024-11-28 11:59 ` Borislav Petkov
2024-11-28 15:52 ` Sasha Levin
2024-11-28 16:08 ` Erwan Velu
2024-11-28 16:43 ` Borislav Petkov
2024-11-29 0:21 ` Sasha Levin
2024-11-29 9:30 ` Erwan Velu
2024-11-29 13:33 ` Borislav Petkov
2024-11-29 15:37 ` Sasha Levin [this message]
2024-11-29 21:18 ` Erwan Velu
2024-11-29 13:30 ` Borislav Petkov
2024-11-29 9:45 ` Pavel Machek
2024-11-29 13:38 ` Sasha Levin
2024-11-29 20:34 ` Pavel Machek
2024-11-29 20:50 ` Sasha Levin
2024-11-29 21:27 ` Pavel Machek
2024-01-15 23:26 ` [PATCH AUTOSEL 5.15 12/12] x86/mce: Mark fatal MCE's page as poison to avoid panic in the kdump kernel Sasha Levin
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=Z0nfomc6TKd-17S9@sashalap \
--to=sashal@kernel.org \
--cc=acdunlap@google.com \
--cc=aik@amd.com \
--cc=ashok.raj@intel.com \
--cc=babu.moger@amd.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=daniel.sneddon@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=erwanaliasr1@gmail.com \
--cc=jmattson@google.com \
--cc=jpoimboe@kernel.org \
--cc=kim.phillips@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=mjguzik@gmail.com \
--cc=nik.borisov@suse.com \
--cc=pavel@denx.de \
--cc=peterz@infradead.org \
--cc=puwen@hygon.cn \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=vegard.nossum@oracle.com \
--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.