linux-kernel - Re: [discuss] [PATCH] x86_64: fix cpu MHz reporting on constant

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070315165047.GY21463@amd.com>
Date:	Thu, 15 Mar 2007 17:50:47 +0100
From:	"Joerg Roedel" <joerg.roedel@....com>
To:	"Andi Kleen" <ak@...e.de>
cc:	discuss@...-64.org, linux-kernel@...r.kernel.org
Subject: Re: [discuss] [PATCH] x86_64: fix cpu MHz reporting on
 constant_tsc cpus

On Thu, Mar 15, 2007 at 12:01:09AM +0100, Andi Kleen wrote:
> On Tuesday 13 March 2007 11:00, Joerg Roedel wrote:
> > From: Mark Langsdorf <mark.langsdorf@....com>
> > From: Joerg Roedel <joerg.roedel@....com>
> > 
> > This patch fixes the reporting of cpu_mhz in /proc/cpuinfo on CPUs with
> > a constant TSC rate and a kernel with disabled cpufreq.
> > 
> > Signed-off-by: Mark Langsdorf <mark.langsdorf@....com>
> > Signed-off-by: Joerg Roedel <joerg.roedel@....com>
> > 
> 
> +       cpu_khz = tsc_khz;
> +       if (cpu_has(&boot_cpu_data, X86_FEATURE_CONSTANT_TSC) &&
> +                       nmi_known_cpu()) {
> +               cpu_khz = tsc_calibrate_cpu_khz(); 
> +       }
>  
> 
> I don't think this will do the right thing on Intel CPUs of which tsc_calibrate_cpu_khz()
> knows nothing about. 

Yes. You are right. I will fix that and send a new version.  Thanks for
the review.

Joerg

-- 
Joerg Roedel
Operating System Research Center
AMD Saxony LLC & Co. KG


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/