From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: paul.gortmaker@windriver.com
Cc: bp@alien8.de, linux-kernel@vger.kernel.org, peterz@infradead.org,
richard.purdie@linuxfoundation.org, tglx@linutronix.de,
x86@kernel.org,
Linux kernel regressions list <regressions@lists.linux.dev>
Subject: Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]
Date: Sat, 11 Nov 2023 12:51:58 +0100 [thread overview]
Message-ID: <0adb772c-e8d2-4444-92b0-00cbfdaf1fac@leemhuis.info> (raw)
In-Reply-To: <ZUEgAAGDVqXz2Seo@windriver.com>
[CCing the regression list, as it should be in the loop for regressions:
https://docs.kernel.org/admin-guide/reporting-regressions.html]
> [Re: 32 bit qemu regression from v6.5 tip pull [6c480f222128 x86/alternative: Rewrite optimize_nops() some]] On 30/10/2023 (Mon 20:30) Thomas Gleixner wrote:
>
>> On Mon, Oct 30 2023 at 19:24, Thomas Gleixner wrote:
>
>> > 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?
>>
>> Forgot to ask: Does the probkem persist with 6.6 ?
>
> My bad, should have mentioned v6.6 and linux-next is impacted. Always a
> conflict between burying the lead and boring people with details.
Paul, was this regression ever solved? I wonder as I could not find
anything with a "Fixes: 6c480f222128 [...]" tag on lore and this thread
looks stalled.
Ciao, Thorsten
next prev parent reply other threads:[~2023-11-11 11:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 18:41 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
2023-10-30 19:30 ` Thomas Gleixner
2023-10-31 15:40 ` Paul Gortmaker
2023-11-11 11:51 ` Linux regression tracking (Thorsten Leemhuis) [this message]
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=0adb772c-e8d2-4444-92b0-00cbfdaf1fac@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=paul.gortmaker@windriver.com \
--cc=peterz@infradead.org \
--cc=regressions@lists.linux.dev \
--cc=richard.purdie@linuxfoundation.org \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®