All of lore.kernel.org
 help / color / mirror / Atom feed
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, 12 Jun 2026 08:42:02 +0200	[thread overview]
Message-ID: <20260612064202.GN187714@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <20260612022158.GDaittRqWfYLGwPHNw@fat_crate.local>

On Thu, Jun 11, 2026 at 07:21:58PM -0700, Borislav Petkov wrote:
> On Thu, Jun 11, 2026 at 08:37:36PM +0200, Peter Zijlstra wrote:
> > 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.
> > 
> > This is somewhat similar to the split lock stuff, yeah, they're bad, but
> > nobody is going to be fixing those games.
> > 
> > And UMIP really is useful; these are gnarly instructions you really
> > don't want, so as along as it all runs it should be fine. I suppose I
> > should go re-enable it on my own machine and actually spend some time on
> > it if/when I find another game that flat out doesn't work with the
> > emulation.
> 
> Yah, I guess... I don't play them games so meh, but sure, makes sense to me.
> I guess we can have people test it and see whether it helps.. maybe...

I have kids, playing games is mandatory ;-) At least I got out of having
to join Fortnite on account of it not running on Linux (silver lining
and all that).

  reply	other threads:[~2026-06-12  6:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-10 19:46 UMIP and clearcpuid= 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 [this message]
2026-06-12 14:49                 ` Borislav Petkov

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=20260612064202.GN187714@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.