From: "Lluís Vilanova" <vilanova@ac.upc.edu>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 6/6] trace: Add QAPI/QMP interfaces to query and control per-vCPU tracing state
Date: Mon, 20 Jun 2016 12:53:11 +0200 [thread overview]
Message-ID: <87oa6wt9m0.fsf@fimbulvetr.bsc.es> (raw)
In-Reply-To: <87y460coi6.fsf@dusky.pond.sub.org> (Markus Armbruster's message of "Mon, 20 Jun 2016 09:23:29 +0200")
Markus Armbruster writes:
> Lluís Vilanova <vilanova@ac.upc.edu> writes:
>> Signed-off-by: Lluís Vilanova <vilanova@ac.upc.edu>
>> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>> ---
>> monitor.c | 4 +-
>> qapi/trace.json | 20 ++++++--
>> qmp-commands.hx | 17 ++++++-
>> trace/qmp.c | 143 ++++++++++++++++++++++++++++++++++++++++++++-----------
>> 4 files changed, 147 insertions(+), 37 deletions(-)
>>
>> diff --git a/monitor.c b/monitor.c
>> index a27e115..bb89877 100644
>> --- a/monitor.c
>> +++ b/monitor.c
>> @@ -910,7 +910,7 @@ static void hmp_trace_event(Monitor *mon, const QDict *qdict)
>> bool new_state = qdict_get_bool(qdict, "option");
>> Error *local_err = NULL;
>>
>> - qmp_trace_event_set_state(tp_name, new_state, true, true, &local_err);
>> + qmp_trace_event_set_state(tp_name, new_state, true, true, false, 0, &local_err);
>> if (local_err) {
>> error_report_err(local_err);
>> }
>> @@ -1069,7 +1069,7 @@ static void hmp_info_cpustats(Monitor *mon, const QDict *qdict)
>>
>> static void hmp_info_trace_events(Monitor *mon, const QDict *qdict)
>> {
>> - TraceEventInfoList *events = qmp_trace_event_get_state("*", NULL);
>> + TraceEventInfoList *events = qmp_trace_event_get_state("*", false, 0, NULL);
>> TraceEventInfoList *elem;
>>
>> for (elem = events; elem != NULL; elem = elem->next) {
> The new feature remains inaccessible in HMP. Any plans to extend HMP?
> Any reasons not to?
BTW, I was just looking at "info trace-events" and it only shows the state for
all events (there's no name pattern argument). Is it worth updating HMP knowing
it should be replaced in favour of the newer QAPI interface?
Thanks,
Lluis
next prev parent reply other threads:[~2016-06-20 10:53 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-14 13:10 [Qemu-devel] [PATCH v4 0/6] trace: Per-vCPU tracing states Lluís Vilanova
2016-06-14 13:10 ` [Qemu-devel] [PATCH v4 1/6] trace: Identify events with the 'vcpu' property Lluís Vilanova
2016-06-14 13:11 ` [Qemu-devel] [PATCH v4 2/6] disas: Remove unused macro '_' Lluís Vilanova
2016-06-14 13:11 ` Lluís Vilanova
2016-06-17 15:25 ` [Qemu-arm] " Stefan Hajnoczi
2016-06-17 15:25 ` [Qemu-devel] " Stefan Hajnoczi
2016-06-14 13:11 ` [Qemu-devel] [PATCH v4 3/6] [trivial] trace: Cosmetic changes on fast-path tracing Lluís Vilanova
2016-06-14 13:11 ` [Qemu-devel] [PATCH v4 4/6] trace: Add per-vCPU tracing states for events with the 'vcpu' property Lluís Vilanova
2016-06-17 15:24 ` Stefan Hajnoczi
2016-06-17 20:16 ` Lluís Vilanova
2016-06-20 12:05 ` Stefan Hajnoczi
2016-06-20 12:40 ` Lluís Vilanova
2016-06-21 9:21 ` Stefan Hajnoczi
2016-06-14 13:11 ` [Qemu-devel] [PATCH v4 5/6] trace: Conditionally trace events based on their per-vCPU state Lluís Vilanova
2016-06-14 13:11 ` [Qemu-devel] [PATCH v4 6/6] trace: Add QAPI/QMP interfaces to query and control per-vCPU tracing state Lluís Vilanova
2016-06-20 7:23 ` Markus Armbruster
2016-06-20 10:48 ` Lluís Vilanova
2016-06-20 12:13 ` Markus Armbruster
2016-06-20 12:44 ` Lluís Vilanova
2016-06-20 10:53 ` Lluís Vilanova [this message]
2016-06-20 12:17 ` Markus Armbruster
2016-06-20 12:37 ` Lluís Vilanova
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=87oa6wt9m0.fsf@fimbulvetr.bsc.es \
--to=vilanova@ac.upc.edu \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@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.