From: Borislav Petkov <bp@alien8.de>
To: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org,
Ricardo Neri <ricardo.neri@intel.com>,
x86@kernel.org, "Ravi V. Shankar" <ravi.v.shankar@intel.com>
Subject: Re: [PATCH] x86/cpufeatures: Add enumeration for serialize instruction
Date: Sat, 4 Apr 2020 10:28:09 +0200 [thread overview]
Message-ID: <20200404082809.GA7356@zn.tnic> (raw)
In-Reply-To: <20200404052039.GA14886@ranerica-svr.sc.intel.com>
On Fri, Apr 03, 2020 at 10:20:39PM -0700, Ricardo Neri wrote:
> Do you mean code in the kernel using this instructions. Thus far, I
> don't have any kernel use cases for this instruction.
I'm sure you can find at least a couple of places in the kernel
which use CPUID to serialize and could switch to this new insn with
alternatives, for example. Or all those memory barrier uses. Would it be
better to switch to SERIALIZE there? Dunno, but would be good to know.
And so on.
> My intention is to expose this instruction to user space via
> /proc/cpuinfo. Is that not acceptable?
I know what your intention is. What good is the string "serialize" in
/proc/cpuinfo if nothing uses it?
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2020-04-04 8:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-03 1:40 [PATCH] x86/cpufeatures: Add enumeration for serialize instruction Ricardo Neri
2020-04-03 8:12 ` Borislav Petkov
2020-04-04 5:20 ` Ricardo Neri
2020-04-04 8:28 ` Borislav Petkov [this message]
2020-04-07 1:36 ` Ricardo Neri
2020-04-04 21:15 ` Andy Lutomirski
2020-04-07 1:38 ` Ricardo Neri
2020-04-07 1:53 ` Andy Lutomirski
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=20200404082809.GA7356@zn.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=ravi.v.shankar@intel.com \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=ricardo.neri@intel.com \
--cc=tglx@linutronix.de \
--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