From: Marcos Del Sol Vives <marcos@orca.pet>
To: Borislav Petkov <bp@alien8.de>
Cc: "Ahmed S. Darwish" <darwi@linutronix.de>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Brian Gerst <brgerst@gmail.com>, Uros Bizjak <ubizjak@gmail.com>,
Ard Biesheuvel <ardb@kernel.org>,
David Kaplan <david.kaplan@amd.com>, Kees Cook <kees@kernel.org>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Oleg Nesterov <oleg@redhat.com>, "Xin Li (Intel)" <xin@zytor.com>,
Sabyrzhan Tasbolatov <snovitoll@gmail.com>
Subject: Re: [PATCH] x86: add hintable NOPs emulation
Date: Wed, 20 Aug 2025 11:51:27 +0200 [thread overview]
Message-ID: <be242e65-b056-4e12-93e7-9a297aaf231a@orca.pet> (raw)
In-Reply-To: <20250820094347.GDaKWY02hR3AAoT7la@fat_crate.local>
El 20/08/2025 a las 11:43, Borislav Petkov escribió:
> On Wed, Aug 20, 2025 at 11:33:05AM +0200, Marcos Del Sol Vives wrote:
>> But I think the kernel should let the user know the binaries they're
>> running are having some performance penalty due to this emulation, in case
>> they want to recompile without the offending flags.
>
> Sure, once perhaps.
>
> Do you want to let the user know for each binary?
>
> And how many users do you really think will look at dmesg and recompile their
> binaries?
I mean, they should know what they need to recompile if they want to, not
just that their machine is having a bug triggered by some binary.
A global flag would mean they'd need to reboot to see if there is any other
binary triggering it too.
Whether they look or not at the dmesg I cannot tell, but if IOPL emulation
does logging this way, I assumed this should too. Otherwise, would that
mean IOPL emulation logging is also too verbose?
next prev parent reply other threads:[~2025-08-20 9:51 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-20 1:34 Marcos Del Sol Vives
2025-08-20 9:07 ` Peter Zijlstra
2025-08-21 12:28 ` David Laight
2025-08-21 12:46 ` Peter Zijlstra
2025-08-21 18:40 ` David Laight
2025-08-21 19:46 ` Marcos Del Sol Vives
2025-08-21 15:11 ` Marcos Del Sol Vives
2025-08-20 9:14 ` Ahmed S. Darwish
2025-08-20 9:33 ` Marcos Del Sol Vives
2025-08-20 9:43 ` Borislav Petkov
2025-08-20 9:51 ` Marcos Del Sol Vives [this message]
2025-08-20 9:55 ` Borislav Petkov
2025-08-20 10:01 ` Marcos Del Sol Vives
2025-08-20 10:08 ` Borislav Petkov
2025-08-20 10:21 ` Marcos Del Sol Vives
2025-08-20 10:30 ` Borislav Petkov
2025-08-21 2:00 ` Kees Cook
2025-08-20 10:11 ` Ahmed S. Darwish
2025-08-20 10:30 ` Ahmed S. Darwish
2025-08-21 1:43 ` H. Peter Anvin
2025-08-21 9:35 ` Marcos Del Sol Vives
2025-08-21 5:02 ` H. Peter Anvin
2025-08-21 12:26 ` David Laight
2025-08-21 12:48 ` Marcos Del Sol Vives
2025-08-21 12:48 ` Peter Zijlstra
2025-08-21 13:45 ` Marcos Del Sol Vives
2025-08-21 13:59 ` Peter Zijlstra
2025-08-22 22:12 ` H. Peter Anvin
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=be242e65-b056-4e12-93e7-9a297aaf231a@orca.pet \
--to=marcos@orca.pet \
--cc=andrew.cooper3@citrix.com \
--cc=ardb@kernel.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=darwi@linutronix.de \
--cc=dave.hansen@linux.intel.com \
--cc=david.kaplan@amd.com \
--cc=hpa@zytor.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=snovitoll@gmail.com \
--cc=tglx@linutronix.de \
--cc=ubizjak@gmail.com \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
/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®