linux-kernel - Re: [PATCH] x86: new Intel Atom SoC power management controller 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: <531808BD.4070000@linux.intel.com>
Date:	Thu, 06 Mar 2014 13:33:49 +0800
From:	"Li, Aubrey" <aubrey.li@...ux.intel.com>
To:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Matthew Garrett <mjg59@...f.ucam.org>, mingo@...hat.com,
	tglx@...utronix.de, linux-kernel@...r.kernel.org,
	"alan@...ux.intel.com" <alan@...ux.intel.com>
Subject: Re: [PATCH] x86: new Intel Atom SoC power management controller driver

On 2014/3/6 13:28, H. Peter Anvin wrote:
> On 03/05/2014 09:21 PM, Li, Aubrey wrote:
>>>
>>> What is the reason for putting this in debugfs?
>>
>> S0ix support on Atom SoC needs all of the devices under south complex to
>> be quiesced, as well as the devices under north complex. This interface
>> shows all of the devices states under platform control unit. If the
>> system is not able to enter S0ix, we have a way to diagnose. Or if the
>> system entered S0ix, we have counters to show S0ix entered and its
>> residency.
>>
> 
> I guess the real question is: are you sure this is only for debugging,
> or is this going to be an interface that applications or daemons will
> actually use (in which case it should live in sysfs).

These interfaces are uncommitted and don't have consumers now, I'd like
to keep them unstable in debugfs.

We can change it if we received a requirement to use them later.

Thanks,
-Aubrey

> 
> 	-hpa
> 
> 
> 
> 

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