From: Randy Dunlap <randy.dunlap@oracle.com>
To: Zhang Rui <rui.zhang@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-pm <linux-pm@lists.linux-foundation.org>,
a.p.zijlstra@chello.nl, mingo@elte.hu, acme@redhat.com,
ming.m.lin@intel.com, "Brown, Len" <lenb@kernel.org>
Subject: Re: [PATCH 2/3] introduce intel_rapl driver
Date: Thu, 26 May 2011 08:48:15 -0700 [thread overview]
Message-ID: <20110526084815.adee4fb1.randy.dunlap@oracle.com> (raw)
In-Reply-To: <1306398857.2207.157.camel@rui>
On Thu, 26 May 2011 16:34:17 +0800 Zhang Rui wrote:
>
> Introduce Intel RAPL driver.
>
> RAPL (running average power limit) is a new feature which provides mechanisms
> to enforce power consumption limit, on some new processors.
>
> RAPL provides MSRs reporting the total amount of energy consumed
> by the package/core/uncore/dram.
> Further more, by using RAPL, OS can set a power bugdet in a certain time window,
> and let Hardware to throttle the processor P/T-state to meet this enery limitation.
>
> Currently, we don't have the plan to support the RAPL power control,
> but we do want to export the package/core/uncore/dram power consumption
> information via perf tool first.
Hi,
What's an uncore?
> Signed-off-by: Zhang Rui <rui.zhang@intel.com>
> ---
> drivers/platform/x86/Kconfig | 8
> drivers/platform/x86/Makefile | 1
> drivers/platform/x86/intel_rapl.c | 368 ++++++++++++++++++++++++++++++++++++++
> include/linux/perf_event.h | 4
> 4 files changed, 381 insertions(+)
>
> Index: linux-2.6/drivers/platform/x86/Kconfig
> ===================================================================
> --- linux-2.6.orig/drivers/platform/x86/Kconfig
> +++ linux-2.6/drivers/platform/x86/Kconfig
> @@ -753,4 +753,12 @@ config SAMSUNG_LAPTOP
> To compile this driver as a module, choose M here: the module
> will be called samsung-laptop.
>
> +config INTEL_RAPL
> + tristate "Intel RAPL Support"
> + depends on X86
> + default y
> + ---help---
> + RAPL, AKA, Running Average Power Limit provides mechanisms to enforce
RAPL (Running Average Power Limit) provides mechanisms to enforce
> + power consumption limit.
> +
> endif # X86_PLATFORM_DEVICES
> Index: linux-2.6/drivers/platform/x86/intel_rapl.c
> ===================================================================
> --- /dev/null
> +++ linux-2.6/drivers/platform/x86/intel_rapl.c
> @@ -0,0 +1,368 @@
[snip]
> +/* show the energy status, in Jelous */
Is that Joules? or what?
> +static int rapl_read_energy(struct rapl_domain *domain)
> +{
> + u64 value;
> + u32 msr = domain->msrs.status;
> +
> + rdmsrl(msr, value);
> + return rapl_unit_xlate(ENERGY_UNIT, value, 0);
> +}
[snip]
> +static int __init intel_rapl_init(void)
> +{
> + enum rapl_domain_id id;
> +
> + /*
> + * RAPL features are only supported on processors have a CPUID
> + * signature with DisplayFamily_DisplayModel of 06_2AH, 06_2DH
> + */
> + if (boot_cpu_data.x86 != 0x06)
> + return -ENODEV;
> +
> + if (boot_cpu_data.x86_model == 0x2A)
> + rapl_domains[RAPL_DOMAIN_PP1].valid = 1;
> + else if (boot_cpu_data.x86_model == 0x2D)
> + rapl_domains[RAPL_DOMAIN_DRAM].valid = 1;
> + else
> + return -ENODEV;
> +
> + if (rapl_check_unit())
> + return -ENODEV;
> +
> + for(id = 0; id < RAPL_DOMAIN_MAX; id++)
space after "for"
> + if (rapl_domains[id].valid)
> + perf_pmu_register(&(rapl_domains[id].pmu), rapl_domains[id].pmu.name, PERF_TYPE_SOFTWARE);
> + return 0;
> +}
> +
> +static void __exit intel_rapl_exit(void)
> +{
> + enum rapl_domain_id id;
> +
> + for(id = 0; id < RAPL_DOMAIN_MAX; id++)
ditto
> + if (rapl_domains[id].valid)
> + perf_pmu_unregister(&(rapl_domains[id].pmu));
> +}
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-05-26 15:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 8:34 [PATCH 2/3] introduce intel_rapl driver Zhang Rui
2011-05-26 9:43 ` Peter Zijlstra
2011-05-26 10:21 ` Peter Zijlstra
2011-05-26 10:55 ` Matt Fleming
2011-06-02 8:04 ` Matt Fleming
2011-05-27 8:26 ` Zhang Rui
2011-05-27 19:56 ` Peter Zijlstra
2011-05-27 19:56 ` Peter Zijlstra
2011-05-30 3:11 ` Zhang Rui
2011-05-26 15:48 ` Randy Dunlap [this message]
2011-05-30 2:40 ` Zhang Rui
2011-05-28 10:17 ` Greg KH
2011-05-30 7:04 ` Zhang 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=20110526084815.adee4fb1.randy.dunlap@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=ming.m.lin@intel.com \
--cc=mingo@elte.hu \
--cc=rui.zhang@intel.com \
/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