|   | 
      | 
  
  
      | 
      | 
  
 
     | 
    | 
  
  
     | 
    | 
  
  
    |   | 
      | 
  
  
    | 
         
xen-devel
Re: [Xen-devel] ac_timer: time to say goodbye?
 
On 23 May 2005, at 21:28, Magenheimer, Dan (HP Labs Fort Collins) wrote:
 
I suspect that the whole functionality of it can be replaced
with a couple of time variables that are checked and
manipulated in the timer interrupt code and a single
scheduler/timer routine in the generic scheduler.
 
 
 We are going to strip out the periodic ticker entirely (at least in 
arch/x86) and have just a programmable one-shot timer. We need to keep 
track of what is the nearest event we care about so we know what to 
program into the one-shot timer.
 I think the interface could be simplified a little (fold 
mod_ac_timer/add_ac_timer into a single function, for example), but the 
implementation is already very pared down. I image it would hardly save 
100 lines, or bytes of hypervisor code, to replace the heap with a 
list, for example.
 -- Keir
_______________________________________________
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)
 
  
 
 
 |  
  
 | 
    | 
  
  
    |   | 
    |