From 53b73d2a3139ee5ada71e8c7099ada19311ae53a Mon Sep 17 00:00:00 2001 From: imp Date: Wed, 9 Nov 2005 16:22:56 +0000 Subject: General consensus is that it would be even better to run this in a thread context. While it doesn't matter too much at the moment, in the future we could be back in the same boat if/when more restrictions are placed (or enforced) in a SWI. Suggested by: njl, bde, jhb, scottl --- sys/kern/subr_power.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sys/kern/subr_power.c') diff --git a/sys/kern/subr_power.c b/sys/kern/subr_power.c index a6eea85..ac6cd71 100644 --- a/sys/kern/subr_power.c +++ b/sys/kern/subr_power.c @@ -84,7 +84,7 @@ power_pm_suspend(int state) state != POWER_SLEEP_STATE_HIBERNATE) return; power_pm_task.ta_context = (void *)(intptr_t)state; - taskqueue_enqueue(taskqueue_swi, &power_pm_task); + taskqueue_enqueue(taskqueue_thread, &power_pm_task); } /* -- cgit v1.1