From: "Marcus Rückert" <mrueckert@suse.com>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: Borislav Petkov <bp@alien8.de>, X86 ML <x86@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86/umip: Add a umip= cmdline switch
Date: Wed, 15 Sep 2021 14:21:23 +0200 [thread overview]
Message-ID: <20210915142123.49f8137b@fortress.home.nordisch.org> (raw)
In-Reply-To: <20210915113410.GA7130@ranerica-svr.sc.intel.com>
On Wed, 15 Sep 2021 04:34:10 -0700
Ricardo Neri <ricardo.neri-calderon@linux.intel.com> wrote:
> > They're all likely old, arcane applications or games run in wine
> > which people have no access to the source code anyway so come to
> > think of it, the once thing is starting to make more sense to me
> > now.
>
> Indeed, no one has reported "modern" application using these
> instructions.
I am not sure if Blizzard Entertainment would tell us why they use this
CPU instruction in Overwatch. And that game is "only" 5 years old.
darix
--
Always remember:
Never accept the world as it appears to be.
Dare to see it for what it could be.
The world can always use more heroes.
next prev parent reply other threads:[~2021-09-15 12:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 20:04 [PATCH] x86/umip: Add a umip= cmdline switch Borislav Petkov
2021-09-11 1:14 ` Ricardo Neri
2021-09-11 9:20 ` Borislav Petkov
2021-09-13 21:38 ` Ricardo Neri
2021-09-14 16:51 ` Borislav Petkov
2021-09-15 11:34 ` Ricardo Neri
2021-09-15 12:21 ` Marcus Rückert [this message]
2021-09-15 13:00 ` Ricardo Neri
2021-09-15 13:14 ` Borislav Petkov
2021-09-15 14:46 ` [PATCH] x86/umip: Downgrade warning messages to debug loglevel Borislav Petkov
2021-09-16 0:27 ` Ricardo Neri
2021-09-23 14:59 ` Borislav Petkov
2021-09-13 21:45 ` [PATCH] x86/umip: Add a umip= cmdline switch Ricardo Neri
2021-09-14 16:52 ` Borislav Petkov
2021-09-23 15:03 ` [tip: x86/cpu] x86/umip: Downgrade warning messages to debug loglevel tip-bot2 for Borislav Petkov
2021-09-25 11:31 ` tip-bot2 for 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=20210915142123.49f8137b@fortress.home.nordisch.org \
--to=mrueckert@suse.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ricardo.neri-calderon@linux.intel.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 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.