public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Sasha Levin <sashal@kernel.org>
Cc: Pavel Machek <pavel@denx.de>, Borislav Petkov <bp@alien8.de>,
	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,
	Erwan Velu <erwanaliasr1@gmail.com>
Subject: Re: [PATCH AUTOSEL 5.15 11/12] x86/barrier: Do not serialize MSR accesses on AMD
Date: Fri, 29 Nov 2024 21:34:53 +0100	[thread overview]
Message-ID: <Z0olbd3OYQnlmW+D@duo.ucw.cz> (raw)
In-Reply-To: <Z0nD6NZc3wmq8_v9@sashalap>

[-- Attachment #1: Type: text/plain, Size: 1943 bytes --]

On Fri 2024-11-29 08:38:48, Sasha Levin wrote:
> On Fri, Nov 29, 2024 at 10:45:48AM +0100, Pavel Machek wrote:
> > Hi!
> > 
> > > > You've missed the 5.10 mail :)
> > > 
> > > You mean in the flood? ;-P
> > > 
> > > > Pavel objected to it so I've dropped it: https://lore.kernel.org/all/Zbli7QIGVFT8EtO4@sashalap/
> > > 
> > > So we're not backporting those anymore? But everything else? :-P
> > > 
> > > And 5.15 has it already...
> > > 
> > > Frankly, with the amount of stuff going into stable, I see no problem with
> > > backporting such patches. Especially if the people using stable kernels will
> > > end up backporting it themselves and thus multiply work. I.e., Erwan's case.
> > 
> > Well, some people would prefer -stable to only contain fixes for
> > critical things, as documented.
> > 
> > stable-kernel-rules.rst:
> > 
> > - It must fix a problem that causes a build error (but not for things
> >   marked CONFIG_BROKEN), an oops, a hang, data corruption, a real
> >   security issue, or some "oh, that's not good" issue.  In short, something
> >   critical.
> > 
> > Now, you are right that reality and documentation are not exactly
> > "aligned". I don't care much about which one is fixed, but I'd really
> > like them to match (because that's what our users expect).
> 
> You should consider reading past the first bullet in that section :)
> 
>   - Serious issues as reported by a user of a distribution kernel may also
>     be considered if they fix a notable performance or interactivity issue.
> 
> It sounds like what's going on here, no?

Is it? I'd not expect this to be visible in anything but
microbenchmarks. Do you have user reports hitting this?

It is not like this makes kernel build 10% slower, is it?
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

  reply	other threads:[~2024-11-29 20:35 UTC|newest]

Thread overview: 27+ 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 ` [PATCH AUTOSEL 5.15 03/12] arm64: irq: set the correct node for VMAP stack 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 ` [PATCH AUTOSEL 5.15 05/12] powerpc: Fix build error due to is_valid_bugaddr() 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 ` [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 ` [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 ` [PATCH AUTOSEL 5.15 10/12] powerpc/lib: Validate size for vector operations 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
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 [this message]
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=Z0olbd3OYQnlmW+D@duo.ucw.cz \
    --to=pavel@denx.de \
    --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=peterz@infradead.org \
    --cc=puwen@hygon.cn \
    --cc=rick.p.edgecombe@intel.com \
    --cc=sashal@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox