From: Ian Campbell <ian.campbell@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: jinsong.liu@alibaba-inc.com,
Oleksandr Dmytryshyn <oleksandr.dmytryshyn@globallogic.com>,
Tim Deegan <tim@xen.org>, xen-devel <xen-devel@lists.xen.org>,
jbeulich@suse.com, jacob.shin@amd.com
Subject: Re: cpufreq implementation for OMAP under xen hypervisor.
Date: Fri, 22 Aug 2014 17:51:04 +0100 [thread overview]
Message-ID: <1408726264.17003.31.camel@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1408221722020.8032@kaball.uk.xensource.com>
On Fri, 2014-08-22 at 17:31 +0100, Stefano Stabellini wrote:
> One thing to keep in mind is that although P states are obviously an
> Intel concept
I'm not sure about P-states but C-states at least even if they were
originally an Intel thing seem to have become more of an ACPI thing
these days and I think they are being used by the ARM ACPI stuff too.
(or am I confused?)
Ian.
next prev parent reply other threads:[~2014-08-22 16:51 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-12 10:57 cpufreq implementation for OMAP under xen hypervisor Oleksandr Dmytryshyn
2014-08-12 12:15 ` Stefano Stabellini
2014-08-12 12:19 ` Oleksandr Dmytryshyn
2014-08-19 14:02 ` Vitaly V. Ch
2014-08-21 23:05 ` Stefano Stabellini
2014-08-22 14:21 ` Vitaly Chernooky
2014-08-22 16:20 ` Stefano Stabellini
2014-08-21 11:00 ` Oleksandr Dmytryshyn
2014-08-21 23:31 ` Stefano Stabellini
2014-08-22 9:02 ` Oleksandr Dmytryshyn
2014-08-22 16:31 ` Stefano Stabellini
2014-08-22 16:51 ` Ian Campbell [this message]
2014-08-29 13:25 ` Oleksandr Dmytryshyn
2014-08-29 15:08 ` Andrii Tseglytskyi
2014-09-02 1:00 ` Stefano Stabellini
2014-09-02 9:06 ` Vitaly Chernooky
2014-09-02 15:43 ` Andrii Tseglytskyi
2014-09-02 18:39 ` Stefano Stabellini
2014-09-02 18:46 ` Andrii Tseglytskyi
2014-09-04 14:43 ` Oleksandr Dmytryshyn
2014-09-04 21:56 ` Stefano Stabellini
2014-09-09 10:19 ` Oleksandr Dmytryshyn
2014-09-09 21:52 ` Stefano Stabellini
2014-09-09 10:32 ` Ian Campbell
2014-09-09 21:41 ` Stefano Stabellini
2014-09-10 9:42 ` Ian Campbell
2014-09-10 10:19 ` Andrii Tseglytskyi
2014-09-10 18:35 ` Stefano Stabellini
2014-09-10 19:31 ` Konrad Rzeszutek Wilk
2014-09-16 13:49 ` Oleksandr Dmytryshyn
2014-09-17 17:06 ` Konrad Rzeszutek Wilk
2014-09-18 9:38 ` Oleksandr Dmytryshyn
2014-09-18 14:59 ` Konrad Rzeszutek Wilk
2014-09-19 9:38 ` Oleksandr Dmytryshyn
2014-09-24 14:36 ` Stefano Stabellini
2014-09-24 14:46 ` Konrad Rzeszutek Wilk
2014-09-25 9:13 ` Oleksandr Dmytryshyn
2014-09-25 9:08 ` Oleksandr Dmytryshyn
2014-09-25 10:14 ` Stefano Stabellini
2014-09-25 11:15 ` Oleksandr Dmytryshyn
2014-09-26 18:13 ` Konrad Rzeszutek Wilk
2014-09-29 9:45 ` Oleksandr Dmytryshyn
2014-09-29 15:18 ` Konrad Rzeszutek Wilk
2014-09-30 10:28 ` Oleksandr Dmytryshyn
2014-09-30 17:37 ` Konrad Rzeszutek Wilk
2014-09-11 9:43 ` Ian Campbell
2014-09-09 13:25 ` Vitaly Chernooky
2014-09-09 21:58 ` Stefano Stabellini
2014-09-10 10:15 ` Andrii Tseglytskyi
2014-09-10 10:24 ` Vitaly Chernooky
2014-09-10 11:18 ` Andrii Tseglytskyi
2014-09-10 18:37 ` Stefano Stabellini
2014-09-11 7:51 ` Vitaly Chernooky
2014-09-10 11:24 ` Vitaly Chernooky
2014-09-10 14:28 ` Vitaly Chernooky
2014-09-10 18:41 ` Stefano Stabellini
2014-09-11 7:48 ` Vitaly Chernooky
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=1408726264.17003.31.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=jacob.shin@amd.com \
--cc=jbeulich@suse.com \
--cc=jinsong.liu@alibaba-inc.com \
--cc=oleksandr.dmytryshyn@globallogic.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).