From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:38192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKMaG-0000up-Hb for qemu-devel@nongnu.org; Thu, 21 Aug 2014 03:15:01 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XKMaB-00089K-NY for qemu-devel@nongnu.org; Thu, 21 Aug 2014 03:14:56 -0400 Received: from mx1.redhat.com ([209.132.183.28]:12266) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XKMaB-00089E-F7 for qemu-devel@nongnu.org; Thu, 21 Aug 2014 03:14:51 -0400 Received: from int-mx11.intmail.prod.int.phx2.redhat.com (int-mx11.intmail.prod.int.phx2.redhat.com [10.5.11.24]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id s7L7Eo49002172 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Thu, 21 Aug 2014 03:14:50 -0400 From: Markus Armbruster References: <20140820153431.15111.3916.stgit@fimbulvetr.bsc.es> <87ppfvqfao.fsf@blackfin.pond.sub.org> <87r40bko80.fsf@fimbulvetr.bsc.es> <871tsbnfww.fsf@blackfin.pond.sub.org> <87fvgrj6zo.fsf@fimbulvetr.bsc.es> Date: Thu, 21 Aug 2014 09:14:47 +0200 In-Reply-To: <87fvgrj6zo.fsf@fimbulvetr.bsc.es> (=?utf-8?Q?=22Llu=C3=ADs?= Vilanova"'s message of "Wed, 20 Aug 2014 21:28:27 +0200") Message-ID: <87y4uijouw.fsf@blackfin.pond.sub.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2] trace: [qmp] Add QAPI/QMP commands to query and control event tracing state List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Cc: Stefan Hajnoczi , Luiz Capitulino Llu=C3=ADs Vilanova writes: > Markus Armbruster writes: > >> Llu=C3=ADs Vilanova writes: >>> Markus Armbruster writes: >>>=20 >>>> Llu=C3=ADs Vilanova writes: >>>>> Also removes old "trace-event", "trace-file" and "info trace-events" = HMP >>>>> commands. >>>=20 >>>> We gain the ability to control trace via QMP, but lose the ability to >>>> control it via HMP, correct? >>>=20 >>> Right. I can keep the HMP commands, but doing so requires exposing >>> the internal >>> trace event identifier number in the QMP interface. Also, >>> "trace-file" cannot be >>> implemented on top of the current QMP commands, and is specific to >>> the "simple" >>> tracing backend. > >> Would rough feature-parity with QMP be feasible with new HMP commands on >> top of the QMP interfaces, completely ignoring HMP backward >> compatibility? > > Except for "trace-file", it would be quite easy, yes. Yes, please! > For "trace-file", w= e can > either keep the current HMP implementation, or add new QMP commands to su= pport > it (I'd rather devote my time to something else, though). trace-file is only available with CONFIG_TRACE_SIMPLE. Losing it would be tolerable, I guess. But I'd keep it as is until its maintenance becomes a burden.