From owner-freebsd-acpi@FreeBSD.ORG  Wed Oct 27 12:29:52 2010
Return-Path: <owner-freebsd-acpi@FreeBSD.ORG>
Delivered-To: freebsd-acpi@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 5BCD1106566C
	for <freebsd-acpi@FreeBSD.org>; Wed, 27 Oct 2010 12:29:52 +0000 (UTC)
	(envelope-from takawata@init-main.com)
Received: from sana.init-main.com (unknown [IPv6:2001:240:28::1])
	by mx1.freebsd.org (Postfix) with ESMTP id B43278FC23
	for <freebsd-acpi@FreeBSD.org>; Wed, 27 Oct 2010 12:29:51 +0000 (UTC)
Received: from ns.init-main.com (localhost [127.0.0.1])
	by sana.init-main.com (8.14.3/8.14.3) with ESMTP id o9RCLoWm095086
	for <freebsd-acpi@FreeBSD.org>; Wed, 27 Oct 2010 21:21:50 +0900 (JST)
	(envelope-from takawata@ns.init-main.com)
Message-Id: <201010271221.o9RCLoWm095086@sana.init-main.com>
To: freebsd-acpi@FreeBSD.org
In-reply-to: Your message of "Wed, 27 Oct 2010 10:56:26 +0300."
	<4CC7DB2A.2090601@FreeBSD.org>
Date: Wed, 27 Oct 2010 21:21:50 +0900
From: Takanori Watanabe <takawata@init-main.com>
Cc: 
Subject: Re: Event based scheduling and USB.
X-BeenThere: freebsd-acpi@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ACPI and power management development <freebsd-acpi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-acpi>
List-Post: <mailto:freebsd-acpi@freebsd.org>
List-Help: <mailto:freebsd-acpi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-acpi>,
	<mailto:freebsd-acpi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Oct 2010 12:29:52 -0000

In message <4CC7DB2A.2090601@FreeBSD.org>, Alexander Motin wrote:
>Takanori Watanabe wrote:
>> In message <4CC732C7.50409@FreeBSD.org>, Alexander Motin wrote:
>>> Most likely you should be able to avoid interrupt sharing using some
>>> additional HPET options, described at hpet(4).
>> 
>> Try to disable using shared IRQ with uhci, the IRQ used by HPET become cpu: 
>> interrupt and certainly load average goes quite low, 
>
>If you mean "cpuX:timer" - then probably you did something wrong and
>system fallen back to LAPIC timer.

Hmm, I restrict the HPET IRQ by setting hint.hpet.X.allowed_irqs
kenv value to 0xff000000 to avoid using shared IRQ (IRQ20).