All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Markus Armbruster <armbru@redhat.com>
Cc: qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v2] trace: [qmp] Add QAPI/QMP commands to query and control event tracing state
Date: Wed, 20 Aug 2014 21:28:27 +0200	[thread overview]
Message-ID: <87fvgrj6zo.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <871tsbnfww.fsf@blackfin.pond.sub.org> (Markus Armbruster's message of "Wed, 20 Aug 2014 21:02:07 +0200")

Markus Armbruster writes:

> Lluís Vilanova <vilanova@ac.upc.edu> writes:
>> Markus Armbruster writes:
>> 
>>> Lluís Vilanova <vilanova@ac.upc.edu> writes:
>>>> Also removes old "trace-event", "trace-file" and "info trace-events" HMP
>>>> commands.
>> 
>>> We gain the ability to control trace via QMP, but lose the ability to
>>> control it via HMP, correct?
>> 
>> 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. For "trace-file", we can
either keep the current HMP implementation, or add new QMP commands to support
it (I'd rather devote my time to something else, though).


Thanks,
  Lluis

-- 
 "And it's much the same thing with knowledge, for whenever you learn
 something new, the whole world becomes that much richer."
 -- The Princess of Pure Reason, as told by Norton Juster in The Phantom
 Tollbooth

  reply	other threads:[~2014-08-20 19:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-20 15:34 [Qemu-devel] [PATCH v2] trace: [qmp] Add QAPI/QMP commands to query and control event tracing state Lluís Vilanova
2014-08-20 16:47 ` Markus Armbruster
2014-08-20 18:30   ` Lluís Vilanova
2014-08-20 19:02     ` Markus Armbruster
2014-08-20 19:28       ` Lluís Vilanova [this message]
2014-08-21  7:14         ` Markus Armbruster

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=87fvgrj6zo.fsf@fimbulvetr.bsc.es \
    --to=vilanova@ac.upc.edu \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.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.