From: Thomas Gleixner <tglx@linutronix.de>
To: Paul Gortmaker <paul.gortmaker@windriver.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Borislav Petkov <bp@alien8.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]
Date: Mon, 30 Oct 2023 19:24:27 +0100 [thread overview]
Message-ID: <877cn4ynms.ffs@tglx> (raw)
In-Reply-To: <ZT/Lmj3xAdwvLE7R@windriver.com>
On Mon, Oct 30 2023 at 11:28, Paul Gortmaker wrote:
> [Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]] On 30/10/2023 (Mon 12:44) Peter Zijlstra wrote:
>
>> Thomas was looking at this and wondered if something like the below
>> would help?
>
> I tested this on a vanilla v6.5.7 baseline, for lack of a better choice
> and got six failures in 136 boots - everything else unchanged - even the
> shell instance that builds the kernel.
While the sync_core() invocation is definitely at the wrong place, I did
not really expect that this cures it.
Can you add "debug-alternative" to the kernel command line and log both
a working and the non-working kernel output. It's noisy :)
Also do you have a .config and the qemu command line handy?
Thanks,
tglx
next prev parent reply other threads:[~2023-10-30 18:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 18:41 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some] Paul Gortmaker
2023-10-30 8:26 ` Peter Zijlstra
2023-10-30 10:55 ` Richard Purdie
2023-10-30 11:44 ` Peter Zijlstra
2023-10-30 15:28 ` Paul Gortmaker
2023-10-30 18:24 ` Thomas Gleixner [this message]
2023-10-30 19:30 ` Thomas Gleixner
2023-10-31 15:40 ` Paul Gortmaker
2023-11-11 11:51 ` Linux regression tracking (Thorsten Leemhuis)
2023-11-22 14:11 ` Richard Purdie
2023-11-29 8:57 ` Thomas Gleixner
2023-12-06 15:46 ` Paul Gortmaker
2023-12-07 16:34 ` Thomas Gleixner
2023-12-07 16:52 ` Paul Gortmaker
2023-12-07 19:49 ` [patch 0/2] x86/alternatives: Prevent crash in NOP optimizer Thomas Gleixner
2023-12-07 19:49 ` [patch 1/2] x86/alternatives: Sync core before enabling interrupts Thomas Gleixner
2023-12-07 19:49 ` [patch 2/2] x86/alternatives: Disable interrupts and sync when optimizing NOPs in place Thomas Gleixner
2023-12-08 13:22 ` Borislav Petkov
2023-12-08 13:37 ` Thomas Gleixner
2023-12-08 8:35 ` [patch 0/2] x86/alternatives: Prevent crash in NOP optimizer Paul Gortmaker
2023-12-15 9:10 ` Peter Zijlstra
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=877cn4ynms.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=richard.purdie@linuxfoundation.org \
--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