[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v13 00/26] COarse-grain LOck-stepping Virtual Machines for Non-stop Service



Changlong Xie writes ("[PATCH v13 00/26] COarse-grain LOck-stepping Virtual 
Machines for Non-stop Service"):
> This patchset implemented the COLO feature for Xen.
> For detail/install/use of COLO feature, refer to:
> http://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
> 
> You can get the codes from here:
> https://github.com/Pating/xen/tree/changlox/colo_v13

I fetched the branches `colo_v13' and `colo_v13_fixup' and it seems
that I can get the proper versions of v13.1 from the latter.  I have
acked them accordingly.

Can you confirm that that branch is what you intend for upstream ?

If so, I have a question about it:

There are two patches in it which have not been posted as part of your
series and are marked as "[DO NOT MERGE]".  (Thanks for your admirably
clear marking, btw.)

They are
  [DONT MERGE] don't create default ioreq server
  [DONT MERGE] tools/libxc: support to resume uncooperative HVM guests


The latter patch "support to resume uncooperative HVM guests" seems to
have been posted a number of times and AFAICT most recently as
  [PATCH v8 05/13] tools/libxc: support to resume uncooperative HVM guests
on the 18th of February.

Is that not required for COLO ?  We need to sort this out, I think.


What is the status of the default ioreq server patch ?  Why is it in
your git branch ?


Thanks,
Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.