linux-kernel - Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot even when ignore

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:	Thu, 16 Apr 2009 12:32:58 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Thomas Renninger <trenn@...e.de>
Cc:	djwong@...ibm.com, linux-kernel <linux-kernel@...r.kernel.org>,
	cpufreq@...r.kernel.org, linux-acpi@...r.kernel.org
Subject: Re: [PATCH v2] acpi: Fix regression where _PPC is not read at boot
	even when ignore_ppc=0


* Thomas Renninger <trenn@...e.de> wrote:

> The *reevaluate* implies that the _PPC value has been 
> evaluated/initialized by the OS already and Ingo's patch would be 
> wrong then. I'd like to have a look at the T60's ACPI parts and 
> find out what exactly (or if at all) makes _PPC to return sane 
> values, I expect it's _PDC.
> 
> Hmm, I could also imagine that Ingo's T60 patch is not needed 
> anymore since Yakui's patch 
> (0ac3c571315a53c14d2733564f14ebdb911fe903). This one could make 
> sure that _PDC is evaluated first making the internal ACPI _PPC 
> state initialize and makes sure _PPC gets only called afterwards.
> 
> If this patch does not break Ingo's T60, I think this should go 
> in. Due to Yakui's reordering/cleanup of ACPI function calls, I 
> think also the notifier chain I introduced is not needed anymore 
> and I can clean this up if I find some time.

Feel free to do so, if it's expected to work. I'll let you know if 
it breaks the T60 box - i still have it in the -tip test mix.

Acked-by: Ingo Molnar <mingo@...e.hu>

	Ingo
--
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/