Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 02 Oct 2012 10:18:33 -0700
From:      Sean Bruno <seanbru@yahoo-inc.com>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        "freebsd-acpi@freebsd.org" <freebsd-acpi@freebsd.org>
Subject:   Re: notify userland about C-state changes
Message-ID:  <1349198313.4246.3.camel@powernoodle.corp.yahoo.com>
In-Reply-To: <504EDBEB.6010104@FreeBSD.org>
References:  <504EDBEB.6010104@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

> The following patch adds only per-CPU notifications.
> 
>     acpi_cpu: explicitly notify userland about c-state changes
> 
> diff --git a/sys/dev/acpica/acpi_cpu.c b/sys/dev/acpica/acpi_cpu.c
> index 82e204a..15201f9 100644
> --- a/sys/dev/acpica/acpi_cpu.c
> +++ b/sys/dev/acpica/acpi_cpu.c
> @@ -1054,6 +1054,8 @@ acpi_cpu_notify(ACPI_HANDLE h, UINT32 notify, void *context)
>      ACPI_SERIAL_BEGIN(cpu);
>      acpi_cpu_set_cx_lowest(sc);
>      ACPI_SERIAL_END(cpu);
> +
> +    acpi_UserNotify("PROCESSOR", sc->cpu_handle, notify);
>  }
> 
>  static int
> 

So quick question, does this happen a lot on a system with a sporadic
workload?  Does this introduce overhead to the system to service the
notification requests?

Sean




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1349198313.4246.3.camel>