on 02/10/2012 20:18 Sean Bruno said the following:
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
---
On Wed, 2012-10-03 at 06:08 -0700, Andriy Gapon wrote:
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?
I am not sure who can answer this question. It is up to ACPI
on 03/10/2012 19:21 Sean Bruno said the following:
On Wed, 2012-10-03 at 06:08 -0700, Andriy Gapon wrote:
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?
I am not sure who can
Please take a look at the following patch and a commit message that explains it.
I observed the problem on a system with acpi_wmi instances where one instance
overrode GUID list from the other.
commit f1f4109b1588872906ed56086e2680ac1af96268
Author: Andriy Gapon a...@icyb.net.ua
Date: Thu Sep
on 03/10/2012 20:40 Ian Smith said the following:
So are you talking about a devd notification to trigger activity like
the AC/battery script, or a sysctl that scripts could poll, or?
devd notification like for AC line status change.
--
Andriy Gapon
