From: Peter Zijlstra <peterz@infradead.org>
To: Huang Rui <ray.huang@amd.com>
Cc: "Borislav Petkov" <bp@suse.de>,
"Andy Lutomirski" <luto@amacapital.net>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Ingo Molnar" <mingo@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
"Len Brown" <lenb@kernel.org>,
"John Stultz" <john.stultz@linaro.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
linux-kernel@vger.kernel.org, x86@kernel.org,
"Fengguang Wu" <fengguang.wu@intel.com>,
"Aaron Lu" <aaron.lu@intel.com>,
"Suravee Suthikulanit" <suravee.suthikulpanit@amd.com>,
"Tony Li" <tony.li@amd.com>, "Ken Xue" <ken.xue@amd.com>
Subject: Re: [PATCH v5 1/2] x86, mwaitt: add monitorx and mwaitx instruction
Date: Mon, 15 Jun 2015 12:55:42 +0200 [thread overview]
Message-ID: <20150615105542.GV3644@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <1434365284-1495-2-git-send-email-ray.huang@amd.com>
On Mon, Jun 15, 2015 at 06:48:03PM +0800, Huang Rui wrote:
> +/*
> + * MWAITT allows for both a timer value to get you out of the MWAIT as
> + * well as the normal exit conditions.
> + *
> + * MWAITX ECX[1]: enable timer if set
> + * MWAITX EBX[31:0]: max wait time expressed in SW P0 clocks
> + *
> + * Below is the compared data between MWAIT and MWAITX on AMD
> + * processors:
> + * MWAIT MWAITX
> + * opcode 0f 01 c9 | 0f 01 fb
> + * ECX[0] value of RFLAGS.IF seen by instruction
> + * ECX[1] unused/#GP if set | enable timer if set
> + * ECX[31:2] unused/#GP if set
> + * EAX unused (reserve for hint)
Seeing how you're stuffing a !0 value in here in the next patch, the
above comment seems slightly incorrect, no?
> + * EBX[31:0] unused | max wait time (loops)
> + *
> + * MONITOR MONITORX
> + * opcode 0f 01 c8 | 0f 01 fa
> + * EAX (logical) address to monitor
> + * ECX #GP if not zero
> + *
> + * The software P0 frequency is the same as the TSC frequency.
> + */
> +static inline void __mwaitx(unsigned long eax, unsigned long ebx,
> + unsigned long ecx)
> +{
> + /* "mwaitx %eax, %ebx, %ecx;" */
> + asm volatile(".byte 0x0f, 0x01, 0xfb;"
> + :: "a" (eax), "b" (ebx), "c" (ecx));
> +}
> +
> static inline void __sti_mwait(unsigned long eax, unsigned long ecx)
> {
> trace_hardirqs_on();
> --
> 1.9.1
>
next prev parent reply other threads:[~2015-06-15 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-15 10:48 [PATCH v5 0/2] x86, mwaitt: introduce AMD mwaitt support Huang Rui
2015-06-15 10:48 ` [PATCH v5 1/2] x86, mwaitt: add monitorx and mwaitx instruction Huang Rui
2015-06-15 10:55 ` Peter Zijlstra [this message]
2015-06-15 12:42 ` Huang Rui
2015-06-15 10:48 ` [PATCH v5 2/2] x86, mwaitt: introduce mwaix delay with a configurable timer Huang Rui
2015-06-15 10:57 ` Peter Zijlstra
2015-06-15 11:15 ` Borislav Petkov
2015-06-15 14:04 ` Huang Rui
2015-06-15 14:25 ` Borislav Petkov
2015-06-15 14:33 ` Huang Rui
2015-06-15 14:14 ` Huang Rui
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=20150615105542.GV3644@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=aaron.lu@intel.com \
--cc=bp@suse.de \
--cc=fengguang.wu@intel.com \
--cc=fweisbec@gmail.com \
--cc=john.stultz@linaro.org \
--cc=ken.xue@amd.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=ray.huang@amd.com \
--cc=rjw@rjwysocki.net \
--cc=suravee.suthikulpanit@amd.com \
--cc=tglx@linutronix.de \
--cc=tony.li@amd.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 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®