lkml.org 
[lkml]   [2007]   [Mar]   [16]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Stolen and degraded time and schedulers

* Jeremy Fitzhardinge <jeremy@goop.org> wrote:

> Ingo Molnar wrote:
> > touching the 'timer tick' is the wrong approach. 'stolen time' only
> > matters to the /scheduler tick/. So extend the hypervisor interface to
> > allow the injection of 'virtual' scheduler tick events: via the use of a
> > special clockevents device - do not change clockevents itself.
>
> I didn't. I was using sloppy terminology: I hang the stolen time
> accounting off the Xen timer interrupt routine, just so that it gets
> run every now and again.

i dont understand: how are you separating 'stolen time' drifts from
events generated for absolute timeouts?

> I suppose I could explicitly hook stolen time accounting into the
> scheduler, but its not obvious to me that it's necessary.

right now i dont see any clean way to solve this problem without having
two clockevents drivers: one for the scheduler, one for timer events.

Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2007-03-16 09:43    [W:0.139 / U:0.044 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site