[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wj4gDw2iMi-OSbCov3SVDJCQr=YCRr3JZr9Mz-eNwfmGw@mail.gmail.com>
Date: Mon, 10 Nov 2025 08:18:02 -0800
From: Linus Torvalds <torvalds@...uxfoundation.org>
To: Peter Zijlstra <peterz@...radead.org>, Ingo Molnar <mingo@...nel.org>
Cc: x86@...nel.org, linux-kernel@...r.kernel.org, kees@...nel.org,
acarmina@...hat.com, jpoimboe@...nel.org, mark.rutland@....com,
maciej.wieczor-retman@...el.com
Subject: Re: [PATCH v2 00/12] x86: WARN() hackery
On Mon, 10 Nov 2025 at 03:58, Peter Zijlstra <peterz@...radead.org> wrote:
>
> We should probably just merge these, as they improve the code-gen for WARN()
> significantly on x86
Yes.. And I'd actually like to see some example code generation in
the commit messages just to make that "improve the code-gen" more
explicit.
I know I saw some originally (or at least we discussed it), but it's
been long enough that my bird-brain has long since forgotten..
It looks like this series is on top of the BUGVERBOSE_DETAILED updates
(that I like but don't have in my tree yet - I think it's all
scheduled for 6.19). So I just scanned the patches visually and they
all look fine, I was just left wanting a more concrete "look, we used
to do this, now we generate _this_ instead".
Linus
Powered by blists - more mailing lists