[Top][All Lists]

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

Re: [Qemu-block] [PATCH] tcmu: Introduce qemu-tcmu utility

From: Kevin Wolf
Subject: Re: [Qemu-block] [PATCH] tcmu: Introduce qemu-tcmu utility
Date: Mon, 11 Mar 2019 12:06:31 +0100
User-agent: Mutt/1.11.3 (2019-02-01)

Am 09.03.2019 um 02:46 hat Yaowei Bai geschrieben:
> Thanks for explaining the background. It comes to my mind that actually we
> talked about these two cases with Fam a bit long time ago and decided to
> support both these two cases. The reason why we implement case2 first is
> currently we care more about exporting new opened images and it's a bit
> more convenient, exporting from a VM or QMP can be added in the later
> release. Do you think it's reasonable/acceptable that we support both
> cases and use case2 for normal new opened images and case1 for the
> circumstances you mention above?

I would like to avoid a second code path because it comes with a
maintenance cost.

Experience also tells that adding a new way to parse option strings will
come back at us later because it we must always maintain compatibility
with yet another format.

So I would prefer not doing this and just passing command line options
to qemu-tcmu, which can reuse the already existing code paths.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]