On Tue, Aug 01, 2017 at 11:32:41PM +0200, Rafael Wysocki wrote: > On Tuesday, August 01, 2017 11:36:18 PM Pali Rohár wrote: > > On Tuesday 01 August 2017 23:20:10 Rafael J. Wysocki wrote: > > > No evaluation of AML methods from user space, please. > > > > > > This is plain dangerous, because you never know what those things do and doing > > > that on production systems is just a plain "no". > > > > > > You can, however, expose the output of AML methods this way or another, > > > for example if they are expected to generate packages of data or similar. > > > > > > The interface for that cannot be "evaluate this random method right now and > > > give me the result", though. > > > > It is not a random AML method. It is _WDG buffer which wmi.ko already > > reads + parse (IIRC only once when doing initialization) and purpose is > > to provide copy of this buffer also to userspace. Similarly like > > wmi-bmof.ko provides MOF buffer. > > OK, then. > Specifically, _WDG is a method which evaluates to a buffer [1], and it is this buffer which Pali would like to see exported via sysfs. This data block provides a description (array of structs) for each data block, event, and control method provided by the WMI GUID. Each includes a 2 char ID, and this ID and data type provide the mapping needed to identify the enable/disable and control ACPI method names. 1. https://msdn.microsoft.com/en-us/library/windows/hardware/Dn614028(v=vs.85).aspx -- Darren Hart VMware Open Source Technology Center
