linux-kernel - Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver

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: <20070516212736.GO15763@ifa.hawaii.edu>
Date:	Wed, 16 May 2007 11:27:36 -1000
From:	Joshua Hoblitt <jhoblitt@....hawaii.edu>
To:	Daniel Drake <dsd@...too.org>
Cc:	Duane Griffin <duaneg@...da.com>,
	Prakash Punnoor <prakash@...noor.de>,
	LKML <linux-kernel@...r.kernel.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH] Kconfig powernow-k8 driver should depend on ACPI P-States driver

On Wed, May 16, 2007 at 04:04:40PM -0400, Daniel Drake wrote:
> Duane Griffin wrote:
> >On 16/05/07, Prakash Punnoor <prakash@...noor.de> wrote:
> >>Maybe you want to give a hint in the p states driver help text?
> >
> >I think a hint is the right thing to do, but in the PowerNow! driver
> >rather than the p states one. How about adding something like this to
> >the X86_POWERNOW_K8 (and X86_POWERNOW_K7?) help text:
> 
> Please hold off this patch until we've gained a more complete 
> understanding of the issues and workarounds (which will probably lead to 
> us writing a better patch anyway)

I agree - the issue is more complicated that I had thought.  I received
an off list message saying that this dependency isn't required on a
single-socket Athlon X2 system.  So it sounds like isn't an SMP setup
issue as much as it is a multi-socket or perhaps just an issue with my
vendor (Tyan).

-J

--

Content of type "application/pgp-signature" skipped