[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 0 of 2] Mem event ring management overhaul
> On Tue, Dec 06, Andres Lagar-Cavilla wrote: > >> If the request comes from the guest itself, and it requires >> paging_populate (!= p2m_query), the event is guaranteed to be put in the >> ring, and then the vcpu goes to sleep. >> >> Easy-peasy > > If everything were so easy. ;-) > > I will try to combine your patch with my paging waitqueue change. > Perhaps your change should disallow paging if max_cpus is larger than > RING_SIZE(). That sounds excellent. I can do those changes as well, if you don't want to be burdened by that. I think it's wise though, to suspend forward-motion on either "branch" of ring management until we get a verdict. The fundamentals of each philosophy have been exposed. Further code has a 50% of being throw-away. Thanks Andres > > > Olaf > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |