From: Fabiano Rosas <farosas@suse.de>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: Laurent Vivier <lvivier@redhat.com>, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH] system/qtest.c: Allow for multiple CHR_EVENT_CLOSED events
Date: Fri, 14 Nov 2025 16:53:02 -0300 [thread overview]
Message-ID: <875xbccrxd.fsf@suse.de> (raw)
In-Reply-To: <CAFEAcA-ROzqrpb1Z9oR2LF5=YHhM95=Ae2RCsqPH7Yj3CRBwLA@mail.gmail.com>
Peter Maydell <peter.maydell@linaro.org> writes:
> Ping for code review?
>
> thanks
> -- PMM
>
> On Fri, 7 Nov 2025 at 17:43, Peter Maydell <peter.maydell@linaro.org> wrote:
>>
>> In the qtest_event() QEMUChrEvent handler, we create a timer
>> and log OPENED on CHR_EVENT_OPENED, and we destroy the timer and
>> log CLOSED on CHR_EVENT_CLOSED. However, the chardev subsystem
>> can send us more than one CHR_EVENT_CLOSED if we're reading from
>> a file chardev:
>> * the first one happens when we read the last data from the file
>> * the second one happens when the user hits ^C to exit QEMU
>> and the chardev is finalized: char_fd_finalize()
>>
>> This causes us to call g_timer_elapsed() with a NULL timer
>> (which glib complains about) and print an extra CLOSED log line
>> with a zero timestamp:
>>
>> [I +0.063829] CLOSED
>> qemu-system-aarch64: GLib: g_timer_elapsed: assertion 'timer != NULL' failed
>> [I +0.000000] CLOSED
>>
>> Avoid this by ignoring a CHR_EVENT_CLOSED if we have already
>> processed one.
>>
>> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
>> ---
>> system/qtest.c | 4 ++++
>> 1 file changed, 4 insertions(+)
>>
>> diff --git a/system/qtest.c b/system/qtest.c
>> index baef06d4d1b..67e2385f4b0 100644
>> --- a/system/qtest.c
>> +++ b/system/qtest.c
>> @@ -815,6 +815,10 @@ static void qtest_event(void *opaque, QEMUChrEvent event)
>> }
>> break;
>> case CHR_EVENT_CLOSED:
>> + if (!qtest_opened) {
>> + /* Ignore CLOSED events if we have already closed the log */
>> + break;
>> + }
>> qtest_opened = false;
>> if (qtest_log_fp) {
>> fprintf(qtest_log_fp, "[I +" FMT_timeval "] CLOSED\n", g_timer_elapsed(timer, NULL));
>> --
>> 2.43.0
I'm aware some qtest stuff is lingering on the list, I came back from
vacations yesterday and will give attention to it in the next few days.
Reviewed-by: Fabiano Rosas <farosas@suse.de>
next prev parent reply other threads:[~2025-11-14 19:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 17:43 [PATCH] system/qtest.c: Allow for multiple CHR_EVENT_CLOSED events Peter Maydell
2025-11-14 13:21 ` Peter Maydell
2025-11-14 19:53 ` Fabiano Rosas [this message]
2025-11-14 14:30 ` Laurent Vivier
2025-11-18 18:32 ` 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=875xbccrxd.fsf@suse.de \
--to=farosas@suse.de \
--cc=lvivier@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@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 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).