From: Fenghua Yu <fenghua.yu@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Fenghua Yu <fenghua.yu@intel.com>, Ingo Molnar <mingo@redhat.com>,
H Peter Anvin <hpa@zytor.com>, Ashok Raj <ashok.raj@intel.com>,
Alan Cox <alan@linux.intel.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Borislav Petkov <bp@alien8.de>
Subject: Re: [RFC PATCH 7/8] x86/lib_user_wait.h: Add APIs for user wait instructions
Date: Tue, 19 Jun 2018 15:27:19 -0700 [thread overview]
Message-ID: <20180619222718.GD112652@romley-ivt3.sc.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.21.1806191109580.1692@nanos.tec.linutronix.de>
On Tue, Jun 19, 2018 at 11:12:05AM +0200, Thomas Gleixner wrote:
> On Fri, 15 Jun 2018, Fenghua Yu wrote:
>
> > A few new user wait instructions UMONITOR, UMWAIT, and TPAUSE are
> > published in the latest Intel Instruction Set Extensions document.
> >
> > Define the APIs for user or kernel to use the instructions.
>
> You're not defining APIs. You're adding a pile of misdesigned helper
> functions which again add static storage per compilation unit and CPUID
> fiddling.
>
> If you want to add proper APIs then add the stuff to the VDSO and be done
> with it.
The user wait instructions are mainly called by user apps; but they can
be used in kernel as well.
I'm planning to provide five APIs to user:
1. If user wait feature is supported
2. nsec to tsc translation
3. umonitor function that exectes UMONITOR instruction
4. umwait function that executes UMWAIT instruction
5. tpause function that executes TPAUSE instruction
Seems 1-2 can be implemented in VDSO. But should I implement 3-5 in
VDSO/kernel as well?
Thanks.
-Fenghua
next prev parent reply other threads:[~2018-06-19 22:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 3:06 [RFC PATCH 0/8] x86: Enable a few new instructions Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 1/8] x86/cpufeatures: Enumerate MOVDIRI instruction Fenghua Yu
2018-06-19 8:57 ` Thomas Gleixner
2018-06-19 21:36 ` Fenghua Yu
2018-06-19 22:32 ` Thomas Gleixner
2018-06-19 22:35 ` Fenghua Yu
2018-06-25 16:13 ` David Laight
2018-06-16 3:06 ` [RFC PATCH 2/8] x86/cpufeatures: Enumerate MOVDIR64B instruction Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 3/8] x86/cpufeatures: Enumerate UMONITOR, UMWAIT, and TPAUSE instructions Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 4/8] cpuidle: Set up maximum umwait time and umwait states Fenghua Yu
2018-06-19 9:03 ` Thomas Gleixner
2018-06-19 15:46 ` Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 5/8] x86/umwait.c: Add sysfs interface to show tsc_khz Fenghua Yu
2018-06-19 9:08 ` Thomas Gleixner
2018-06-19 15:11 ` Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 6/8] x86/lib_direct_store.h: Add APIs for direct store instructions Fenghua Yu
2018-06-19 8:47 ` Thomas Gleixner
2018-06-16 3:06 ` [RFC PATCH 7/8] x86/lib_user_wait.h: Add APIs for user wait instructions Fenghua Yu
2018-06-19 9:12 ` Thomas Gleixner
2018-06-19 22:27 ` Fenghua Yu [this message]
2018-06-19 22:34 ` Thomas Gleixner
2018-06-19 22:36 ` Fenghua Yu
2018-06-16 3:06 ` [RFC PATCH 8/8] selftests/x86: Self test for the APIs in lib_direct_store.h and lib_user_wait.h Fenghua Yu
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=20180619222718.GD112652@romley-ivt3.sc.intel.com \
--to=fenghua.yu@intel.com \
--cc=alan@linux.intel.com \
--cc=ashok.raj@intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=ravi.v.shankar@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
all inboxes | Powered by JetHome®