From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>, qemu-devel@nongnu.org
Cc: gson@gson.org, 1654137@bugs.launchpad.net
Subject: Re: [Qemu-devel] [PATCH] char: fix ctrl-a b not working
Date: Tue, 10 Jan 2017 12:22:49 +0100 [thread overview]
Message-ID: <bf314a15-d2aa-f0bb-8a59-5589e623d650@redhat.com> (raw)
In-Reply-To: <20170110110621.15287-1-marcandre.lureau@redhat.com>
On 10/01/2017 12:06, Marc-André Lureau wrote:
> CharDriverState.be should be updated to point to the current
> associated backend.
>
> Fix the regression introduced in the "mux" chardev from commit
> a4afa548fc6dd9842ed86639b4d37d4d1c4ad480.
>
> https://bugs.launchpad.net/bugs/1654137
Queued.
However, can you also simplify mux_chr_accept_input, mux_chr_can_read
and mux_chr_read to use d->be directly, with this change?
Thanks,
Paolo
> Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
> ---
> qemu-char.c | 15 ++++++++++-----
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git a/qemu-char.c b/qemu-char.c
> index 2c9940cea4..676944a765 100644
> --- a/qemu-char.c
> +++ b/qemu-char.c
> @@ -499,7 +499,7 @@ void qemu_chr_fe_printf(CharBackend *be, const char *fmt, ...)
>
> static void remove_fd_in_watch(CharDriverState *chr);
> static void mux_chr_set_handlers(CharDriverState *chr, GMainContext *context);
> -static void mux_set_focus(MuxDriver *d, int focus);
> +static void mux_set_focus(CharDriverState *chr, int focus);
>
> static int null_chr_write(CharDriverState *chr, const uint8_t *buf, int len)
> {
> @@ -666,7 +666,7 @@ static int mux_proc_byte(CharDriverState *chr, MuxDriver *d, int ch)
> case 'c':
> assert(d->mux_cnt > 0); /* handler registered with first fe */
> /* Switch to the next registered device */
> - mux_set_focus(d, (d->focus + 1) % d->mux_cnt);
> + mux_set_focus(chr, (d->focus + 1) % d->mux_cnt);
> break;
> case 't':
> d->timestamps = !d->timestamps;
> @@ -826,8 +826,10 @@ static void mux_chr_set_handlers(CharDriverState *chr, GMainContext *context)
> context, true);
> }
>
> -static void mux_set_focus(MuxDriver *d, int focus)
> +static void mux_set_focus(CharDriverState *chr, int focus)
> {
> + MuxDriver *d = chr->opaque;
> +
> assert(focus >= 0);
> assert(focus < d->mux_cnt);
>
> @@ -836,6 +838,7 @@ static void mux_set_focus(MuxDriver *d, int focus)
> }
>
> d->focus = focus;
> + chr->be = d->backends[focus];
> mux_chr_send_event(d, d->focus, CHR_EVENT_MUX_IN);
> }
>
> @@ -935,7 +938,9 @@ void qemu_chr_fe_deinit(CharBackend *b)
>
> if (b->chr) {
> qemu_chr_fe_set_handlers(b, NULL, NULL, NULL, NULL, NULL, true);
> - b->chr->be = NULL;
> + if (b->chr->be == b) {
> + b->chr->be = NULL;
> + }
> if (b->chr->is_mux) {
> MuxDriver *d = b->chr->opaque;
> d->backends[b->tag] = NULL;
> @@ -999,7 +1004,7 @@ void qemu_chr_fe_take_focus(CharBackend *b)
> }
>
> if (b->chr->is_mux) {
> - mux_set_focus(b->chr->opaque, b->tag);
> + mux_set_focus(b->chr, b->tag);
> }
> }
>
>
next prev parent reply other threads:[~2017-01-10 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 11:06 [Qemu-devel] [PATCH] char: fix ctrl-a b not working Marc-André Lureau
2017-01-10 11:22 ` Paolo Bonzini [this message]
2017-01-10 14:50 ` Marc-André Lureau
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=bf314a15-d2aa-f0bb-8a59-5589e623d650@redhat.com \
--to=pbonzini@redhat.com \
--cc=1654137@bugs.launchpad.net \
--cc=gson@gson.org \
--cc=marcandre.lureau@redhat.com \
--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).