Adding Juergen, to make sure he is aware of the discussion, as this is an excellent summary of the status of this series.
> On 14 Jan 2019, at 14:46, Wei Liu <wei.l...@citrix.com> wrote: > > Hi all > > The locking scheme seems to be remaining sticking point. The rest are > mostly cosmetic issues (FAOD, they still need to be addressed). Frankly > I don't think there is enough time to address all the technical details, > but let me sum up each side's position and see if we can reach an > amicable solution. snip > To unblock this, how about we make Christopher maintainer of Argo? He > and OpenXT will be on the hook for further improvement. And I believe it > would be in their best interest to keep Argo bug-free and eventually > make it become supported. > > So: > > 1. Make sure Argo is self-contained -- this requires careful review for > interaction between Argo and other parts of the hypervisor. > 2. Argo is going to be experimental and off-by-default -- this is the > default status for new feature anyway. > 3. Make Christopher maintainer of Argo -- this would be a natural thing > to do anyway. > > Does this work for everyone? I think this is a good way forward. Thank you Wei for putting this mail together. Best Regards Lars _______________________________________________ Xen-devel mailing list Xen-devel@lists.xenproject.org https://lists.xenproject.org/mailman/listinfo/xen-devel
