From: "Alex Bennée" <alex.bennee@linaro.org>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Stefan Hajnoczi" <stefanha@redhat.com>,
qemu-devel@nongnu.org, "Kyle Evans" <kevans@freebsd.org>,
libvir-list@redhat.com,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Greg Kurz" <groug@kaod.org>, "Eric Blake" <eblake@redhat.com>,
"Warner Losh" <imp@bsdimp.com>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Michael Roth" <michael.roth@amd.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Christian Schoenebeck" <qemu_oss@crudebyte.com>,
"Riku Voipio" <riku.voipio@iki.fi>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Yanan Wang" <wangyanan55@huawei.com>
Subject: Re: [PATCH v5 05/10] qapi: make the vcpu parameters deprecated for 8.1
Date: Thu, 25 May 2023 13:43:56 +0100 [thread overview]
Message-ID: <874jo0vavj.fsf@linaro.org> (raw)
In-Reply-To: <87353kskvz.fsf@pond.sub.org>
Markus Armbruster <armbru@redhat.com> writes:
> Alex Bennée <alex.bennee@linaro.org> writes:
>
>> I don't think I can remove the parameters directly but certainly mark
>> them as deprecated.
>>
>> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
>> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
>> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>> Message-Id: <20230523125000.3674739-6-alex.bennee@linaro.org>
>>
>> ---
>> v5
>> - reword match description
>> - fix reference to return for set operation
>> ---
>> docs/about/deprecated.rst | 9 +++++++++
>> qapi/trace.json | 40 +++++++++++++++++----------------------
>> 2 files changed, 26 insertions(+), 23 deletions(-)
>>
>> diff --git a/docs/about/deprecated.rst b/docs/about/deprecated.rst
>> index e934e0a13a..e44cde057f 100644
>> --- a/docs/about/deprecated.rst
>> +++ b/docs/about/deprecated.rst
>> @@ -254,6 +254,15 @@ it. Since all recent x86 hardware from the past >10 years is capable of the
>> QEMU API (QAPI) events
>> ----------------------
>
> Not this patch's fault: the headline should be "QEMU Machine Protocol
> (QMP) events". The section should directly follow section "QEMU Machine
> Protocol (QMP) commands".
>
> I'd go one step farther, and fuse the two sections under the heading
> "QEMU Machine Protocol (QMP)".
>
>>
>> +``vcpu`` trace events (since 8.1)
>> +'''''''''''''''''''''''''''''''''
>> +
>> +The ability to instrument QEMU helper functions with vcpu aware trace
>
> Should this be "vCPU-aware"?
>
>> +points was removed in 7.0. However the QAPI still exposed the vcpu
>
> s/the QAPI/QMP/
>
>> +parameter. This argument has now been deprecated and the remaining
>> +used trace points converted to plain trace points selected just by
>
> "remaining trace points that used it"?
>
>> +name.
>> +
>> ``MEM_UNPLUG_ERROR`` (since 6.2)
>> ''''''''''''''''''''''''''''''''''''''''''''''''''''''''
>>
>> diff --git a/qapi/trace.json b/qapi/trace.json
>> index 6bf0af0946..e561f3d3da 100644
>> --- a/qapi/trace.json
>> +++ b/qapi/trace.json
>> @@ -37,13 +37,14 @@
>> #
>> # @vcpu: Whether this is a per-vCPU event (since 2.7).
>> #
>> -# An event is per-vCPU if it has the "vcpu" property in the
>> -# "trace-events" files.
>> +# Features:
>> +# @deprecated: Member @vcpu is deprecated, and always false.
>> #
>> # Since: 2.2
>> ##
>> { 'struct': 'TraceEventInfo',
>> - 'data': {'name': 'str', 'state': 'TraceEventState', 'vcpu': 'bool'} }
>> + 'data': {'name': 'str', 'state': 'TraceEventState',
>> + 'vcpu': { 'type': 'bool', 'features': ['deprecated'] } } }
>>
>> ##
>> # @trace-event-get-state:
>> @@ -52,19 +53,15 @@
>> #
>> # @name: Event name pattern (case-sensitive glob).
>> #
>> -# @vcpu: The vCPU to query (any by default; since 2.7).
>> +# @vcpu: The vCPU to query (since 2.7).
>> #
>> -# Returns: a list of @TraceEventInfo for the matching events
>> -#
>> -# An event is returned if:
>> +# Features:
>> +# @deprecated: Member @vcpu is deprecated, and always false.
>
> This isn't quite right: parameter @vcpu cannot be false, it's int.
>
> I figure specifying the parameter makes no sense anymore, because if you
> do, the command will return an empty list. Correct?
Well its not longer checked so I guess "and always ignored" would be
more correct.
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2023-05-25 12:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 13:39 [PATCH v5 00/10] tracing: remove dynamic vcpu state Alex Bennée
2023-05-24 13:39 ` [PATCH v5 01/10] *-user: remove the guest_user_syscall tracepoints Alex Bennée
2023-05-24 13:39 ` [PATCH v5 02/10] trace-events: remove the remaining vcpu trace events Alex Bennée
2023-05-24 13:39 ` [PATCH v5 03/10] trace: remove vcpu_id from the TraceEvent structure Alex Bennée
2023-05-24 13:39 ` [PATCH v5 04/10] scripts/qapi: document the tool that generated the file Alex Bennée
2023-05-24 13:56 ` Philippe Mathieu-Daudé
2023-05-25 11:19 ` Markus Armbruster
2023-05-25 19:25 ` Stefan Hajnoczi
2023-05-24 13:39 ` [PATCH v5 05/10] qapi: make the vcpu parameters deprecated for 8.1 Alex Bennée
2023-05-25 11:36 ` Markus Armbruster
2023-05-25 12:43 ` Alex Bennée [this message]
2023-05-24 13:39 ` [PATCH v5 06/10] trace: remove code that depends on setting vcpu Alex Bennée
2023-05-24 13:39 ` [PATCH v5 07/10] trace: remove control-vcpu.h Alex Bennée
2023-05-24 13:39 ` [PATCH v5 08/10] tcg: remove the final vestiges of dstate Alex Bennée
2023-05-24 13:39 ` [PATCH v5 09/10] hw/9pfs: use qemu_xxhash4 Alex Bennée
2023-05-24 13:39 ` [PATCH v5 10/10] accel/tcg: include cs_base in our hash calculations Alex Bennée
2023-05-26 16:15 ` Richard Henderson
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=874jo0vavj.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=eduardo@habkost.net \
--cc=groug@kaod.org \
--cc=imp@bsdimp.com \
--cc=kevans@freebsd.org \
--cc=libvir-list@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=michael.roth@amd.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu_oss@crudebyte.com \
--cc=richard.henderson@linaro.org \
--cc=riku.voipio@iki.fi \
--cc=stefanha@redhat.com \
--cc=wangyanan55@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).