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

Re: [Xen-ia64-devel] Question domU blocking and xen timer interrupt

To: Atsushi SAKAI <sakaia@xxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Question domU blocking and xen timer interrupt
From: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxxxxxxx>
Date: Tue, 16 Jan 2007 14:35:10 +0100
Cc: xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Jan 2007 05:34:56 -0800
Domainkey-signature: s=s768; d=fujitsu-siemens.com; c=nofws; q=dns; b=NNab+Wm0Ud4UuHDHf/LVQd6iSpFF4J2U8NFDd1jh785wQHNASy+UYfTbMrwhVuQHd1qhQOdeO19YXC33uSpUhvJLJbyHhDH6xFfN04/vKbmvC3kCCUzLECXbJpJD8muN;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <200701160220.l0G2KUnf008570@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <51CFAB8CB6883745AE7B93B3E084EBE207DE05@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200701160220.l0G2KUnf008570@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.5
> Hi, Dietmar
>
>  As you suggested.
> Currently HYPERVISOR_set_timer_op is not used.
>
> for more detail, please see following mail.
> http://lists.xensource.com/archives/html/xen-ia64-devel/2006-07/msg00056.ht
>ml
>
> Thanks
> Atsushi SAKAI

Thanks for your hint.
I tried the PAL_HALT_LIGHT call and the domU gets blocked and woken up when 
the time is over or a key is pressed. But I don't see a timer event for this 
cr.itm.
I looked at the xen code and saw that your function hlt_timer_fn() was changed 
later and the part
if(vcpu_timer_expired(v)){
                vcpu_pend_timer(v);
        }
was removed. What caused this?
How do I get this timer event?
In the current form - how do I know  whether the block was finished by a timer 
event or any other event (maybe the key press event)?
Thanks.

Dietmar.

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