From: Borislav Petkov <bp@alien8.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Breno Leitao <leitao@debian.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
vlad.wing@gmail.com, security@kernel.org, kernel-team@meta.com
Subject: Re: [PATCH 6.18.y] x86/cpufeatures: Make X86_FEATURE leaf 17 Linux-specific
Date: Fri, 13 Nov 2026 00:15:30 +0000 [thread overview]
Message-ID: <804E3306-237D-4923-BF96-9E7C85BB933D@alien8.de> (raw)
In-Reply-To: <87ik21sirc.ffs@fw13>
On November 13, 2026 12:00:07 AM UTC, Thomas Gleixner <tglx@linutronix.de> wrote:
>Yes. The fact that it's ridiculous that we still have to debate this.
I don't think anyone disagrees.
>The time wasted on that, the time wasted by people to decode the subtle
>bugs and the amount of AI tokens wasted to come up with more duct tape
>fixes is at least an order of magnitude more expensive than funding the
>completion of the overhaul.
There's a great proverb in my native tongue which goes something like this: whack the saddle so that the horse hears and acts on it.
Yeah, I'm just a saddle. :-)
>But I just "work" here so I might be missing something important which
>justifies that ...
Same here. Lemme continue working towards it and we'll see where we get. I'll whack scattered.c and then continue working on Ahmed's pile. Unless you have a different suggestion.
Thx.
--
Small device. Typos and formatting crap
prev parent reply other threads:[~2026-11-13 0:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 16:06 Breno Leitao
2026-11-12 4:57 ` Borislav Petkov
2026-11-12 22:13 ` H. Peter Anvin
2026-11-12 22:23 ` Borislav Petkov
2026-11-12 23:09 ` Thomas Gleixner
2026-11-12 23:33 ` Borislav Petkov
2026-11-13 0:00 ` Thomas Gleixner
2026-11-13 0:15 ` Borislav Petkov [this message]
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=804E3306-237D-4923-BF96-9E7C85BB933D@alien8.de \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=kernel-team@meta.com \
--cc=kvm@vger.kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=security@kernel.org \
--cc=tglx@linutronix.de \
--cc=vlad.wing@gmail.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
all inboxes | Powered by JetHome®