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]
Date:	Fri, 22 Jul 2011 16:43:09 +0200
From:	Borislav Petkov <bp@...64.org>
To:	Matthew Garrett <mjg@...hat.com>
Cc:	"cpufreq@...r.kernel.org" <cpufreq@...r.kernel.org>,
	"davej@...hat.com" <davej@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Langsdorf, Mark" <mark.langsdorf@....com>,
	"Herrmann3, Andreas" <Andreas.Herrmann3@....com>
Subject: Re: [PATCH v4 6/7] cpufreq: Remove support for hardware P-state
 chips from powernow-k8

On Mon, Jul 18, 2011 at 12:37:41PM -0400, Matthew Garrett wrote:

...

>         /* min/max the cpu is capable of */
> @@ -1334,18 +1165,10 @@ static int __cpuinit powernowk8_cpu_init(struct cpufreq_policy *pol)
>                 return -EINVAL;
>         }
> 
> -       /* Check for APERF/MPERF support in hardware */
> -       if (cpu_has(c, X86_FEATURE_APERFMPERF))
> -               cpufreq_amd64_driver.getavg = cpufreq_get_measured_perf;
> -

Btw, this makes cpufreq_get_measured_perf used only in acpi-cpufreq now
and <drivers/cpufreq/mperf.c> can be merged into acpi-cpufreq, thus
removing linking it into both drivers in <drivers/cpufreq/Makefile>.

Also, can you put the next set of patches in a git repo somewhere so
that I could pull them for testing instead of applying them one by one?

Thanks.

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ