On 03/13/2017 03:10 PM, Zhang Chen wrote:
On 03/13/2017 02:28 PM, Jason Wang wrote:
On 2017年03月13日 14:18, Zhang Chen wrote:
Hi~~~ All~
No news for a long time, anyone can give me some comments?
Hi,
A question is why use two kinds of colo-frames? This seems not good
as lots of the code were duplicated.
Because Xen colo-frame based on Xen Remus.
Remus do some job like the migration job in qemu/kvm, and in Xen HVM
we can not do migration in qemu,
So colo-frame code must running in Xen side.
In addition, Xen HVM use qemu to simulation device that Colo-proxy and
Replication can use same one codes in qemu.
Detail:
https://wiki.xenproject.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
Thanks
Zhang Chen
Thanks
Zhang Chen
Thanks
Thanks
Zhang Chen
On 02/28/2017 06:48 PM, Zhang Chen wrote:
This series focus on COLO Xen support.
We add a new chardev socket in colo-compare as the way
of communicate with Xen COLO-frame.
Xen part:
https://lists.xenproject.org/archives/html/xen-devel/2017-02/msg02067.html
This series is a frame, have some TODO job depend on this patch:
https://lists.nongnu.org/archive/html/qemu-devel/2017-02/msg05055.html
Zhang Chen (3):
COLO-compare: Add new parameter for communicate with Xen colo-frame
COLO-compare: Add Xen notify chardev socket handler frame
COLO-compare: Add colo-compare Xen notify
net/colo-compare.c | 77
++++++++++++++++++++++++++++++++++++++++++++++++++++++
qemu-options.hx | 38 ++++++++++++++++++++++++---
2 files changed, 111 insertions(+), 4 deletions(-)
.
--
Thanks
Zhang Chen
