From: Keir Fraser <keir@xensource.com>
Subject: Re: [PATCH] linux: fix condition for entering
	tickless state
Date: Fri, 09 Mar 2007 17:42:41 +0000
Message-ID: <C2174D11.B28C%keir@xensource.com>
References: <45F19F49.76E4.0078.0@novell.com>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <45F19F49.76E4.0078.0@novell.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: Jan Beulich <jbeulich@novell.com>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org




On 9/3/07 16:54, "Jan Beulich" <jbeulich@novell.com> wrote:

> I noticed that timer interrupts were running at full rate regardless
> of whether the system was idle.
> softlockup_get_next_event() must return the maximum of zero and the
> delta to the next event, not the minimum (which is always zero or
> negative, yielding zero or a very large positive number as return
> value).

Oops. :-)

 K.