From: Dario Faggioli <dario.faggioli@citrix.com>
To: "Zhang Chen" <zhangckid@gmail.com>,
山本真吾 <yamamoto.140387@gmail.com>,
xen-devel@lists.xen.org
Cc: xiecl.fnst@cn.fujitsu.com, imhy.yang@gmail.com,
zhangchen.fnst@cn.fujitsu.com, wency@cn.fujitsu.com
Subject: Re: How to prepare the COLO test environment
Date: Tue, 19 Sep 2017 10:32:28 +0200 [thread overview]
Message-ID: <1505809948.3483.6.camel@citrix.com> (raw)
In-Reply-To: <CAK3tnv+shhpTB6Rgd4OV=KGoL5+1ZMYfRpLf7AbOzw+0Z2LC_A@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1237 bytes --]
On Mon, 2017-09-18 at 18:52 +0000, Zhang Chen wrote:
> 山本真吾 <yamamoto.140387@gmail.com>于2017年9月18日周一 下午6:27写道：
> > I have read the following documents:
> >
> > COLO - Coarse Grain Lock Stepping
> > https://wiki.xen.org/wiki/COLO_-_Coarse_Grain_Lock_Stepping
> >
> > Mailing list
> > https://lists.xen.org/archives/html/xen-devel/2016-03/msg00376.html
> >
> > If there are some mistakes in English, I'd like apologize.
> > Thank you.
> >
>
> Unfortunately, wiki and the mail can't be updated. Latest COLO use
> user space COLO-Proxy in qemu,
> Wiki just guide you to setup kernel space COLO-Proxy(this version
> COLO-proxy not being maintained).
>
I'm not sure what you mean with "wiki...can't be updated". If you're
saying that neither you nor anyone that you know have the time or the
knowledge to update it, then fine.
But, technically, the Wiki can be updated and, if possible, it should
be.
Regards,
Dario
--
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
[-- Attachment #2: Type: text/plain, Size: 127 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-19 8:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 10:24 How to prepare the COLO test environment 山本真吾
2017-09-18 18:52 ` Zhang Chen
2017-09-19 8:32 ` Dario Faggioli [this message]
2017-09-19 13:11 ` Zhang Chen
2017-10-05 5:57 ` 山本真吾
2017-10-09 1:23 ` Zhang Chen
2017-10-11 17:37 ` Zhang Chen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1505809948.3483.6.camel@citrix.com \
--to=dario.faggioli@citrix.com \
--cc=imhy.yang@gmail.com \
--cc=wency@cn.fujitsu.com \
--cc=xen-devel@lists.xen.org \
--cc=xiecl.fnst@cn.fujitsu.com \
--cc=yamamoto.140387@gmail.com \
--cc=zhangchen.fnst@cn.fujitsu.com \
--cc=zhangckid@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.