On 9 Aug 2013, at 15:35, Paolo Bonzini wrote: > The point is that you can get rid altogether of TimerListGroup if you > just stick the array in the AioContext. There's no use in adding a > concept with an easy plan to delete it, only waiting for someone willing > to do the work. It is not related to anything that Stefan is > doing---the concept of TimerListGroup is introduced by this series.
I don't think that's correct. Timers currently operate only outside of AioContexts and that's what we're maintaining. You're saying make them work only inside AioContexts and add another AioContext to paper over the hole that's there because we have two nested event loops. What I'm saying is if don't have 2 nested event loops (i.e. once Stefan has done his stuff), we won't need the main_loop_tlg then, and removing it will be easy. What I don't want to do is have all the worry about breaking things I don't fully understand by requiring that everything has an AioContext that uses timers now. -- Alex Bligh