[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] Re: [PATCH] libxenlight: clone context to avoid GC corruption
Well. I'm just a humble contributor :) But if you feel like nacking this patch, it'd be nice if you provided either a new "GC", or an alternate way to keep using the old "GC" while using a separate xenstore handle in functions like libxl_xs_read. Or an alternate solution to the watch problem. Thanks, Andres > On Wed, Dec 02, 2009 at 10:09:10PM +0000, Andres Lagar-Cavilla wrote: >> Provide a function to clone a context. This is necessary >> because simply copying the structs will eventually >> corrup the GC: maxsize is updated in the cloned context >> but not in the originating one, yet they have the same >> array of referenced pointers alloc_ptrs. > > I think this doesn't answer the question of why you need this function > at all. I don't think you should clone the context nor share it. > > -- > Vincent > _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |