From: "Alex Bennée" <alex.bennee@linaro.org>
To: Roman Penyaev <r.peniaev@gmail.com>
Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH v7 1/4] chardev/char-pty: send CHR_EVENT_CLOSED on disconnect
Date: Tue, 21 Jan 2025 15:14:17 +0000 [thread overview]
Message-ID: <87r04wnqra.fsf@draig.linaro.org> (raw)
In-Reply-To: <20250118164056.830721-2-r.peniaev@gmail.com> (Roman Penyaev's message of "Sat, 18 Jan 2025 17:40:49 +0100")
Roman Penyaev <r.peniaev@gmail.com> writes:
> Change makes code symmetric to the code, which handles
> the "connected" state, i.e. send CHR_EVENT_CLOSED when
> state changes from "connected" to "disconnected".
>
> This behavior is similar to char-socket, for example.
>
> Signed-off-by: Roman Penyaev <r.peniaev@gmail.com>
> Cc: "Marc-André Lureau" <marcandre.lureau@redhat.com>
> Cc: qemu-devel@nongnu.org
> ---
> chardev/char-pty.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/chardev/char-pty.c b/chardev/char-pty.c
> index cbb21b76ae8d..10a6ee94d55c 100644
> --- a/chardev/char-pty.c
> +++ b/chardev/char-pty.c
> @@ -181,6 +181,9 @@ static void pty_chr_state(Chardev *chr, int connected)
>
> if (!connected) {
> remove_fd_in_watch(chr);
> + if (s->connected) {
> + qemu_chr_be_event(chr, CHR_EVENT_CLOSED);
> + }
> s->connected = 0;
> /* (re-)connect poll interval for idle guests: once per second.
> * We check more frequently in case the guests sends data to
> @@ -215,7 +217,6 @@ static void char_pty_finalize(Object *obj)
> pty_chr_state(chr, 0);
> object_unref(OBJECT(s->ioc));
> pty_chr_timer_cancel(s);
> - qemu_chr_be_event(chr, CHR_EVENT_CLOSED);
> }
It would be nice to clean up connected/s->connected to bools at some
point. However this is fine:
Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
--
Alex Bennée
Virtualisation Tech Lead @ Linaro
next prev parent reply other threads:[~2025-01-21 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 16:40 [PATCH v7 0/4] chardev: implement backend chardev multiplexing Roman Penyaev
2025-01-18 16:40 ` [PATCH v7 1/4] chardev/char-pty: send CHR_EVENT_CLOSED on disconnect Roman Penyaev
2025-01-21 15:14 ` Alex Bennée [this message]
2025-01-18 16:40 ` [PATCH v7 2/4] chardev/char-hub: implement backend chardev aggregator Roman Penyaev
[not found] ` <CAMxuvaxUDzGN1H-zUccQrEz0KvG+a_9t1iKVz4YJQrsdwr=WKA@mail.gmail.com>
2025-01-21 10:56 ` Roman Penyaev
2025-01-22 14:44 ` Alex Bennée
2025-01-22 15:17 ` Roman Penyaev
2025-01-18 16:40 ` [PATCH v7 3/4] tests/unit/test-char: add unit tests for hub chardev backend Roman Penyaev
2025-01-18 16:40 ` [PATCH v7 4/4] qemu-options.hx: describe hub chardev and aggregation of several backends Roman Penyaev
2025-01-21 15:02 ` Alex Bennée
2025-01-21 15:23 ` Roman Penyaev
2025-01-21 15:49 ` Roman Penyaev
2025-01-21 16:02 ` Alex Bennée
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=87r04wnqra.fsf@draig.linaro.org \
--to=alex.bennee@linaro.org \
--cc=marcandre.lureau@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=r.peniaev@gmail.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.