public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
Cc: linux-acpi@vger.kernel.org, cpufreq@vger.kernel.orgt
Subject: Re: [patch 2/2] acpi x86: Make aperf/mperf MSR access in acpi_cpufreq read_only
Date: Tue, 07 Apr 2009 01:35:27 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.2.00.0904070135120.5698@localhost.localdomain> (raw)
In-Reply-To: <20090406182724.072503000@intel.com>

applied

(and cpufreq@vger.kernel.org cc'd)

thanks,
Len Brown, Intel Open Source Technology Center

On Mon, 6 Apr 2009, venkatesh.pallipadi@intel.com wrote:

> Not write zeroes to APERF and MPERF by ondemand governor. With this
> change, other users can share these MSRs for reads.
> 
> Signed-off-by: Venkatesh Pallipadi <venkatesh.pallipadi@intel.com>
> ---
>  arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c |   15 ++++++++++-----
>  1 files changed, 10 insertions(+), 5 deletions(-)
> 
> diff --git a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> index 340bdbe..9d3af38 100644
> --- a/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> +++ b/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.c
> @@ -68,6 +68,7 @@ struct acpi_cpufreq_data {
>  	unsigned int max_freq;
>  	unsigned int resume;
>  	unsigned int cpu_feature;
> +	u64 saved_aperf, saved_mperf;
>  };
>  
>  static DEFINE_PER_CPU(struct acpi_cpufreq_data *, drv_data);
> @@ -259,9 +260,6 @@ static long read_measured_perf_ctrs(void *_cur)
>  	rdmsr(MSR_IA32_APERF, cur->aperf.split.lo, cur->aperf.split.hi);
>  	rdmsr(MSR_IA32_MPERF, cur->mperf.split.lo, cur->mperf.split.hi);
>  
> -	wrmsr(MSR_IA32_APERF, 0, 0);
> -	wrmsr(MSR_IA32_MPERF, 0, 0);
> -
>  	return 0;
>  }
>  
> @@ -281,13 +279,20 @@ static long read_measured_perf_ctrs(void *_cur)
>  static unsigned int get_measured_perf(struct cpufreq_policy *policy,
>  				      unsigned int cpu)
>  {
> -	struct perf_pair cur;
> +	struct perf_pair readin, cur;
>  	unsigned int perf_percent;
>  	unsigned int retval;
>  
> -	if (!work_on_cpu(cpu, read_measured_perf_ctrs, &cur))
> +	if (!work_on_cpu(cpu, read_measured_perf_ctrs, &readin))
>  		return 0;
>  
> +	cur.aperf.whole = readin.aperf.whole -
> +				per_cpu(drv_data, cpu)->saved_aperf;
> +	cur.mperf.whole = readin.mperf.whole -
> +				per_cpu(drv_data, cpu)->saved_mperf;
> +	per_cpu(drv_data, cpu)->saved_aperf = readin.aperf.whole;
> +	per_cpu(drv_data, cpu)->saved_mperf = readin.mperf.whole;
> +
>  #ifdef __i386__
>  	/*
>  	 * We dont want to do 64 bit divide with 32 bit kernel
> -- 
> 1.6.0.6
> 
> -- 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2009-04-07  5:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-06 18:26 [patch 0/2] acpi x86: Make aperf mperf MSR usage in acpi_cpufreq read only venkatesh.pallipadi
2009-04-06 18:26 ` [patch 1/2] acpi x86: Cleanup acpi_cpufreq structures related to aperf/mperf venkatesh.pallipadi
2009-04-07  5:34   ` Len Brown
2009-04-06 18:26 ` [patch 2/2] acpi x86: Make aperf/mperf MSR access in acpi_cpufreq read_only venkatesh.pallipadi
2009-04-07  5:35   ` Len Brown [this message]

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=alpine.LFD.2.00.0904070135120.5698@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=cpufreq@vger.kernel.orgt \
    --cc=linux-acpi@vger.kernel.org \
    --cc=venkatesh.pallipadi@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