linux-kernel - RE: [PATCH 2/2] i7300

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: <7E82351C108FA840AB1866AC776AEC4637CD28F4@orsmsx505.amr.corp.intel.com>
Date:	Tue, 21 Oct 2008 16:02:03 -0700
From:	"Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
CC:	Len Brown <lenb@...nel.org>, Ingo Molnar <mingo@...e.hu>,
	"linux-acpi@...r.kernel.org" <linux-acpi@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	"Henroid, Andrew D" <andrew.d.henroid@...el.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, Andi Kleen <ak@...ux.intel.com>
Subject: RE: [PATCH 2/2] i7300_idle driver v1.55



>-----Original Message-----
>From: Randy Dunlap [mailto:randy.dunlap@...cle.com]
>Sent: Tuesday, October 21, 2008 3:15 PM
>To: Pallipadi, Venkatesh
>Cc: Randy Dunlap; Len Brown; Ingo Molnar;
>linux-acpi@...r.kernel.org; Linux Kernel Mailing List;
>Henroid, Andrew D; Linus Torvalds; Thomas Gleixner; H. Peter
>Anvin; Andi Kleen
>Subject: Re: [PATCH 2/2] i7300_idle driver v1.55
>
>Pallipadi, Venkatesh wrote:
>> Thanks for the review. Some comments below.
>>
>> Thanks,
>> Venki
>>
>>> What is debugfs used for?  any docs for it?
>>
>> It has some statistics about how many times we went
>> into "memory throttling" state and how long we stayed
>> there since the boot. And one tunable that tunes a
>> parameter changing the policy to start throttling.
>> Will document this with an update patch.
>
>"Normal" tunables should be in sysfs, not debugfs.
>Or is this just a debugging tunable?
>
>You surely can't be certain (or require) that debugfs
>be available.
>

The lone tunable is debug only. It needs driver to be
compiled with DEBUG flag to be present in debugfs.
We don't want export it in sysfs and some random user
app starts using it and then end up providing backward
compatibility for it in future.

The other two read only variables give some stats about
the driver usage and also kind of debuggish info that
we used during development. Didn't seem worthy enough
to go under sysfs.

Thanks,
Venki
--
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/