On Wednesday, March 29, 2017 06:13:15 PM Prashanth Prakash wrote:
> Add support to expose idle statistics maintained by platform to
> userspace via sysfs in addition to other data of interest from
> each LPI(Low Power Idle) state.
>
> LPI described in section 8.4.4 of ACPI spec 6.1 provides different
> methods to obtain idle statistics maintained by the platform. These
> show a granular view of how each of the LPI state is being used at
> different level of hierarchy. sysfs data is exposed at each level in
> the hierarchy by creating a directory named 'lpi' at each level and
> the LPI state information is presented under it. Below is the
> representation of LPI information at one such level in the hierarchy
>
> .../ACPI00XX: XX/lpi
> |-> summary_stats
> |-> state0
> | |-> desc
> | |-> time
> | |-> usage
> | |-> latency
> | |-> min_residency
> | |-> flags
> | |-> arch_flags
> |
> <<more states>>
>
> ACPI00XX can be ACPI0007(processor) or ACPI0010(processor container)
>
> stateX contains information related to a specific LPI state defined
> in the LPI ACPI tables.
>
> summary_stats shows the stats(usage and time) from all the LPI states
> under a device. The summary_stats are provided to reduce the number'
> of files to be accessed by the userspace to capture a snapshot of the'
> idle statistics.
>
> Signed-off-by: Prashanth Prakash <pprakash@xxxxxxxxxxxxxx>
I'd like Sudeep to tell me what he thinks about this in the first place.
> ---
> drivers/acpi/acpi_processor.c | 11 ++
> drivers/acpi/processor_idle.c | 345 +++++++++++++++++++++++++++++++++++++++++-
> include/acpi/processor.h | 27 ++++
> 3 files changed, 381 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/acpi/acpi_processor.c b/drivers/acpi/acpi_processor.c
> index 0143135..a01368d 100644
> --- a/drivers/acpi/acpi_processor.c
> +++ b/drivers/acpi/acpi_processor.c
> @@ -570,9 +570,19 @@ void __init acpi_early_processor_osc(void)
> static int acpi_processor_container_attach(struct acpi_device *dev,
> const struct acpi_device_id *id)
> {
> + if (dev->status.present && dev->status.functional &&
> + dev->status.enabled && dev->status.show_in_ui)
> + acpi_lpi_sysfs_init(dev->handle,
> + (struct acpi_lpi_sysfs_data **)&dev->driver_data);
This isn't the right place to do it IMO.
It should be done at the processor driver initialization when it is know that
LPI is going to be used at all.
> return 1;
> }
>
> +static void acpi_processor_container_detach(struct acpi_device *dev)
> +{
> + if (dev->driver_data)
> + acpi_lpi_sysfs_exit((struct acpi_lpi_sysfs_data *)dev->driver_data);
And analogously here.
> +}
> +
> static const struct acpi_device_id processor_container_ids[] = {
> { ACPI_PROCESSOR_CONTAINER_HID, },
> { }
Thanks,
Rafael
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
