LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: "X86 ML" <x86@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
"Marcus Rückert" <mrueckert@suse.com>
Subject: Re: [PATCH] x86/umip: Add a umip= cmdline switch
Date: Tue, 14 Sep 2021 18:51:22 +0200 [thread overview]
Message-ID: <YUDTCgEOZ3JOMSl7@zn.tnic> (raw)
In-Reply-To: <20210913213836.GA10627@ranerica-svr.sc.intel.com>
On Mon, Sep 13, 2021 at 02:38:36PM -0700, Ricardo Neri wrote:
> That is right. Although, I am not sure programs you can have in
> the same machine that also want to use UMIP-protected instructions.
Sure, another game. :-P
But srsly, looking at those two:
umip_pr_warn(regs, "%s instruction cannot be used by applications.\n",
umip_insns[umip_inst]);
umip_pr_warn(regs, "For now, expensive software emulation returns the result.\n");
Why are they there at all?
I mean, I can hardly imagine userspace doing anything about them.
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.
Sure, that:
umip_pr_err(regs, "segfault in emulation. error%x\n",
X86_PF_USER | X86_PF_WRITE);
should be issued unconditionally but I'm wondering if those warning
messages are needed at all. And if not, I should probably simply rip
them all out.
Or at least silence them by default and flip the cmdline switch logic to
enable them for users who are interested in those things but they should
be silent by default.
I.e., you'd need to supply
umip=warnings_on
on the cmdline to actually see them.
Hmmm?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2021-09-14 16:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-07 20:04 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 [this message]
2021-09-15 11:34 ` Ricardo Neri
2021-09-15 12:21 ` Marcus Rückert
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=YUDTCgEOZ3JOMSl7@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mrueckert@suse.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=x86@kernel.org \
--subject='Re: [PATCH] x86/umip: Add a umip= cmdline switch' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).