From: Huang Rui <ray.huang@amd.com>
To: Borislav Petkov <bp@suse.de>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
"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 2/2] x86, mwaitt: introduce mwaix delay with a configurable timer
Date: Mon, 15 Jun 2015 22:33:08 +0800 [thread overview]
Message-ID: <20150615143307.GA28898@hr-slim.amd.com> (raw)
In-Reply-To: <20150615142559.GC4481@pd.tnic>
On Mon, Jun 15, 2015 at 04:25:59PM +0200, Borislav Petkov wrote:
> On Mon, Jun 15, 2015 at 10:04:19PM +0800, Huang Rui wrote:
> > Hmm, the current processor cannot enter C1 with MWAITX, so I don't
> > confirm if it would have higher wakeup latency on C1 in future.
>
> I remember you saying MWAITX enters currently something between C1 and
> C0. How does that behave wrt latency and power savings?
>
Yes, right. The power consumption is less than C0 (C0 > MWAITX > C1).
The waiting exit speed is faster than HTL.
Thanks,
Rui
next prev parent reply other threads:[~2015-06-15 14:34 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
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 [this message]
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=20150615143307.GA28898@hr-slim.amd.com \
--to=ray.huang@amd.com \
--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=peterz@infradead.org \
--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®