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-devel

Re: [Xen-devel] Periodic timer interrupts in the Mini-OS (working?)

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] Periodic timer interrupts in the Mini-OS (working?)
From: Simon Kagstrom <simon.kagstrom@xxxxxx>
Date: Thu, 2 Feb 2006 09:40:00 +0100
Delivery-date: Thu, 02 Feb 2006 08:50:02 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20060202081454.GA20631@xxxxxxxxxxxxxxxxx>
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: <20060202081454.GA20631@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On 2006-02-02, 09:14, Simon Kagstrom wrote:
> Hello!
> 
> I have a question about timer interrupts in the Mini-OS and
> HYPERVISOR_set_timer_op. From printouts, it seems like the Mini-OS only
> recieves timer events after calling block_domain:
> 
> void block_domain(u32 millisecs)
> {
>     struct timeval tv;
>     gettimeofday(&tv);
>     HYPERVISOR_set_timer_op(monotonic_clock() + 1000000LL * (s64) millisecs);
>     HYPERVISOR_sched_op(SCHEDOP_block, 0);
> }
> 
> i.e., not the "regular" 10ms periodic events (if I don't call block_domain(),
> it will just sit idle). I'm trying to understand why this is the case.

It turned out it was my fault, for some reason I had modified do_event() to
include a mask_evtchn(port) in the end. So then, naturally, there were no more
events...

Sorry about the fuss, I should have checked the changes first.

-- 
// Simon

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

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