-----Original Message-----
From: Vladimir Sementsov-Ogievskiy <vsementsov@yandex-team.ru>
Sent: Friday, April 14, 2023 5:51 PM
To: Zhang, Chen <chen.zhang@intel.com>; qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org; pbonzini@redhat.com; armbru@redhat.com;
eblake@redhat.com; jasowang@redhat.com; dgilbert@redhat.com;
quintela@redhat.com; hreitz@redhat.com; kwolf@redhat.com; Zhang,
Hailiang <zhanghailiang@xfusion.com>; lizhijian@fujitsu.com;
wencongyang2@huawei.com; xiechanglong.d@gmail.com; den-
plotnikov@yandex-team.ru
Subject: Re: [PATCH] replication: compile out some staff when replication is
not configured
On 14.04.23 04:24, Zhang, Chen wrote:
So, if I want to have an option to disable all COLO modules, do you
mean it should be additional --disable-colo option? Or better keep
one option -- disable-replication (and, maybe just rename to to --disable-
colo)?
I think keep the option --disable-replication is enough.
Generally speaking, these three modules do not belong to COLO, It has
been decoupled at the time of design.
Instead, COLO is formed when these three modules are used in
combination.
But it's not enough to me, I want to have a possibility to not build the
subsystem I don't need.