All of lore.kernel.org
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: qemu-devel@nongnu.org,  michael.roth@amd.com,  jsnow@redhat.com,
	eblake@redhat.com,  Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 21/28] qapi run-state: Elide redundant has_FOO in generated C
Date: Tue, 18 Oct 2022 15:04:46 +0200	[thread overview]
Message-ID: <87h7012sgh.fsf@pond.sub.org> (raw)
In-Reply-To: <8266adb1-ea48-4ef7-eadc-9aa1e1dde842@linaro.org> ("Philippe Mathieu-Daudé"'s message of "Tue, 18 Oct 2022 14:11:20 +0200")

Philippe Mathieu-Daudé <philmd@linaro.org> writes:

> On 18/10/22 08:28, Markus Armbruster wrote:
>> The has_FOO for pointer-valued FOO are redundant, except for arrays.
>> They are also a nuisance to work with.  Recent commit "qapi: Start to
>> elide redundant has_FOO in generated C" provided the means to elide
>> them step by step.  This is the step for qapi/run-state.json.
>> Said commit explains the transformation in more detail.  The invariant
>> violations mentioned there do not occur here.
>
> The rationale here is qapi free() has always be able to deal with a NULL
> argument (commit fb3182ce6e "qapi: add qapi-types.py code generator"
> from Tue Jul 19 14:50:40 2011).
>
>> Cc: Paolo Bonzini <pbonzini@redhat.com>
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
>> ---
>>   softmmu/runstate.c     | 18 +++++-------------
>>   scripts/qapi/schema.py |  1 -
>>   2 files changed, 5 insertions(+), 14 deletions(-)
>> diff --git a/softmmu/runstate.c b/softmmu/runstate.c
>> index 1e68680b9d..682a810d3c 100644
>> --- a/softmmu/runstate.c
>> +++ b/softmmu/runstate.c
>
>> @@ -517,13 +514,8 @@ void qemu_system_guest_panicked(GuestPanicInformation *info)
>>   void qemu_system_guest_crashloaded(GuestPanicInformation *info)
>>   {
>>       qemu_log_mask(LOG_GUEST_ERROR, "Guest crash loaded");
>> -
>> -    qapi_event_send_guest_crashloaded(GUEST_PANIC_ACTION_RUN,
>> -                                   !!info, info);
>> -
>> -    if (info) {
>> -        qapi_free_GuestPanicInformation(info);
>> -    }
>> +    qapi_event_send_guest_crashloaded(GUEST_PANIC_ACTION_RUN, info);
>> +    qapi_free_GuestPanicInformation(info);
>>   }

Yes, dropping the conditional is an unrelated, but trivial cleanup, and
mentioning such things in the commit message is good practice.

> Preferably updating the commit description:

Intend to add "Drop a superfluous conditional around
qapi_free_GuestPanicInformation() while there."  Okay?

> Reviewed-by: Philippe Mathieu-Daudé <philmd@linaro.org>

Thanks!



  reply	other threads:[~2022-10-18 13:10 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18  6:28 [PATCH v2 00/28] qapi: Elide redundant has_FOO in generated C Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 01/28] docs/devel/qapi-code-gen: Update example to match current code Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 02/28] qapi: Tidy up whitespace in generated code Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 03/28] docs/devel/qapi-code-gen: Extend example for next commit's change Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 04/28] qapi: Start to elide redundant has_FOO in generated C Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 05/28] qapi tests: Elide " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 06/28] qapi acpi: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 07/28] qapi audio: " Markus Armbruster
2022-10-18 12:15   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 08/28] qapi block: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 09/28] qapi char: " Markus Armbruster
2022-10-18 12:14   ` Philippe Mathieu-Daudé
2022-10-18 12:55     ` Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 10/28] qapi crypto: " Markus Armbruster
2022-10-18 11:57   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 11/28] qapi dump: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 12/28] qapi job: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 13/28] qapi machine: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 14/28] qapi migration: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 15/28] qapi misc: " Markus Armbruster
2022-10-18 10:32   ` Dr. David Alan Gilbert
2022-10-18 11:10     ` Markus Armbruster
2022-10-18 11:17       ` Dr. David Alan Gilbert
2022-10-18 13:01         ` Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 16/28] qapi net: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 17/28] qapi pci: " Markus Armbruster
2022-10-18 12:12   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 18/28] qapi qdev qom: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 19/28] qapi replay: " Markus Armbruster
2022-10-18 12:11   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 20/28] qapi rocker: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 21/28] qapi run-state: " Markus Armbruster
2022-10-18 12:11   ` Philippe Mathieu-Daudé
2022-10-18 13:04     ` Markus Armbruster [this message]
2022-10-18  6:28 ` [PATCH v2 22/28] qapi stats: " Markus Armbruster
2022-10-18 12:02   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 23/28] qapi tpm: " Markus Armbruster
2022-10-18 12:01   ` Philippe Mathieu-Daudé
2022-10-18 12:12     ` Stefan Berger
2022-10-18 12:23       ` Philippe Mathieu-Daudé
2022-10-18 13:06         ` Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 24/28] qapi transaction: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 25/28] qapi ui: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 26/28] qapi virtio: " Markus Armbruster
2022-10-18 12:04   ` Philippe Mathieu-Daudé
2022-10-18  6:28 ` [PATCH v2 27/28] qapi qga: " Markus Armbruster
2022-10-18  6:28 ` [PATCH v2 28/28] qapi: Drop temporary logic to support conversion step by step Markus Armbruster
2022-10-18 12:03   ` Philippe Mathieu-Daudé

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=87h7012sgh.fsf@pond.sub.org \
    --to=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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.