On 2013-07-25 20:53, Alex Bligh wrote: > > > --On 25 July 2013 14:32:59 +0200 Jan Kiszka <jan.kis...@siemens.com> wrote: > >>> I would happily at a QEMUClock of each type to AioContext. They are >>> after >>> all pretty lightweight. >> >> What's the point of adding tones of QEMUClock instances? Considering >> proper abstraction, how are they different for each AioContext? Will >> they run against different clock sources, start/stop at different times? >> If the answer is "they have different timer list", then fix this >> incorrect abstraction. > > Even if I fix the abstraction, there is a question of whether it is > necessary to have more than one timer list per AioContext, because > the timer list is fundamentally per clock-source.
So far. Once we support different handler thread for timers, there will be more lists than clock sources. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux
