[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <924EFEDD5F540B4284297C4DC59F3DEE38C313@orsmsx423.amr.corp.intel.com>
Date: Fri, 7 Dec 2007 13:38:00 -0800
From: "Pallipadi, Venkatesh" <venkatesh.pallipadi@...el.com>
To: "Pavel Machek" <pavel@....cz>
Cc: "Andrew Morton" <akpm@...ux-foundation.org>, <lkml@....ca>,
<abelay@...ell.com>, <lenb@...nel.org>, <mlord@...ox.com>,
<rjw@...k.pl>, <linux-kernel@...r.kernel.org>,
<linux-acpi@...r.kernel.org>
Subject: RE: + restore-missing-sysfs-max_cstate-attr.patch added to -mm tree
>-----Original Message-----
>From: Pavel Machek [mailto:pavel@....cz]
>Sent: Wednesday, December 05, 2007 3:17 AM
>To: Pallipadi, Venkatesh
>Cc: Andrew Morton; lkml@....ca; abelay@...ell.com;
>lenb@...nel.org; mlord@...ox.com; rjw@...k.pl;
>linux-kernel@...r.kernel.org; linux-acpi@...r.kernel.org
>Subject: Re: + restore-missing-sysfs-max_cstate-attr.patch
>added to -mm tree
>
>Hi!
>
>> >It is not known whether Mark is actually writing to this
>> >thing. Perhaps
>> >read-only permissions would be a suitable fix?
>> >
>>
>> Exporting it as read only should be OK. We also need to know if there
>> are hard user space dependency on writing to this from userspace.
>
>Some people are manipulating it from their suspend scripts..
>
That is done by default in kernel now. Deep C-states are disabled
between suspend and resume.
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/
Powered by blists - more mailing lists