|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
RE: [Xen-devel] ac_timer: time to say goodbye?
 
> Of the top of my head:
> Each domain has a timer to schedule timeout values. So 
> depending on how many
> domains are blocking the number of timers varies.
> Then there is one timer per vcpu to generate a ticker for the 
> currently
> running VM.
Every domain or every *active* domain?
For inactive domains, determining when the next ticker
should be delivered could be part of the domain context,
with next tick scheduled when it is made active.
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
 
 |   
 
| <Prev in Thread] | 
Current Thread | 
[Next in Thread>
 |  
- [Xen-devel] ac_timer: time to say goodbye?, Magenheimer, Dan (HP Labs Fort Collins)
- RE: [Xen-devel] ac_timer: time to say goodbye?, Ian Pratt
 
- RE: [Xen-devel] ac_timer: time to say goodbye?, Magenheimer, Dan (HP Labs Fort Collins)
 
- RE: [Xen-devel] ac_timer: time to say goodbye?,
Magenheimer, Dan (HP Labs Fort Collins) <=
 
- RE: [Xen-devel] ac_timer: time to say goodbye?, Magenheimer, Dan (HP Labs Fort Collins)
 
- RE: [Xen-devel] ac_timer: time to say goodbye?, Ian Pratt
 
- RE: [Xen-devel] ac_timer: time to say goodbye?, Magenheimer, Dan (HP Labs Fort Collins)
 
- RE: [Xen-devel] ac_timer: time to say goodbye?, Magenheimer, Dan (HP Labs Fort Collins)
 
  
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |