From: Peter Zijlstra <peterz@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Ronan Pigott <ronan@rjp.ie>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: UMIP and clearcpuid=
Date: Fri, 14 Aug 2026 14:19:47 +0200 [thread overview]
Message-ID: <20260814121947.GJ788244@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260611183736.GI187714@noisy.programming.kicks-ass.net>
On Thu, Jun 11, 2026 at 08:37:36PM +0200, Peter Zijlstra wrote:
> On Thu, Jun 11, 2026 at 09:09:46AM -0700, Borislav Petkov wrote:
>
> > > It is really annoying having to disable UMIP though, its bugged me, just
> > > not enough to ever actually do anything about it.
> >
> > Well, what else could we do? Whitelist processes, make it more fine-grained or
> > so...?
>
> Perhaps just one print per task might be a good start? Something like
> so?
>
> I don't think anything hits this hard enough to matter performance wise;
> but the wine stuff can hit them often enough that the dmesg spam is
> annoying, and there's really nothing much you can do about it.
Apparently some games are hitting this rather hard:
https://www.reddit.com/r/linux_gaming/comments/1qdj79f/is_mhwilds_performance_throttled_by_an_expensive/
That seems to suggest the game is doing DLC checks on *EVERY* frame
while in a settlement. That's absolutely bonkers, but whatever.
prev parent reply other threads:[~2026-08-14 12:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 19:46 Ronan Pigott
2026-06-10 20:00 ` Borislav Petkov
2026-06-10 20:41 ` Ronan Pigott
2026-06-10 23:55 ` Borislav Petkov
2026-06-11 7:53 ` Peter Zijlstra
2026-06-11 16:09 ` Borislav Petkov
2026-06-11 18:37 ` Peter Zijlstra
2026-06-12 2:21 ` Borislav Petkov
2026-06-12 6:42 ` Peter Zijlstra
2026-06-12 14:49 ` Borislav Petkov
2026-08-14 11:50 ` Peter Zijlstra
2026-08-14 12:12 ` Peter Zijlstra
2026-08-14 12:57 ` Andrew Cooper
2026-08-14 13:23 ` Peter Zijlstra
2026-08-17 21:39 ` Kenny Wottrich
2026-08-14 12:19 ` Peter Zijlstra [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=20260814121947.GJ788244@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ronan@rjp.ie \
--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®