WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-devel] Announcing OpenBSD/amd64 Xen port

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Announcing OpenBSD/amd64 Xen port
From: Mathieu Ropert <mro@xxxxxxxxxx>
Date: Fri, 09 Jun 2006 11:54:20 +0200
Cc: misc@xxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 12 Jun 2006 01:37:44 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <c553df5c595e4c653432badc48f1ef8a@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4487F26A.10506@xxxxxxxxxx> <c553df5c595e4c653432badc48f1ef8a@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 1.0.2 (Windows/20050317)
Keir Fraser wrote:


On 8 Jun 2006, at 10:48, Mathieu Ropert wrote:

- events/clock issue: there seems to be a race condition leading to clock not ticking, hence putting system to sleep till a keyboard/network/disk interrupt is received.


The ticker doesn't tick when you block. Your idle loop needs to disable interrupts, set a one-shot timer, then block. See safe_halt() in our Linux source tree (arch/i386/kernel/time-xen.c) -- the function expects to be called with interrupts disabled and caller should also have already checked for any other threads being runnable.

 -- Keir

Thanks! That solved my issue. Just disabling interrupts before i call my idle function did the trick.

Mathieu

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>