[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag
From: |
Peter Xu |
Subject: |
Re: [Qemu-devel] [PATCH 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag |
Date: |
Wed, 10 Oct 2018 11:54:11 +0800 |
User-agent: |
Mutt/1.10.1 (2018-07-13) |
On Tue, Oct 09, 2018 at 05:12:48PM +0400, Marc-André Lureau wrote:
> The feature should be set if the chardev is able to switch
> GMainContext. Callers that want to put a chardev in a different thread
> context can/should check this capabilities.
IIRC we've had some discussion about whether we should allow to
dynamically switch context for chardevs, and a (temporarily)
conclusion is that we'd prefer to forbidden it for simplicity
(although it's still allowed in current master). Does this patch mean
that we'd still want to allow that for some future scenarios?
>
> Signed-off-by: Marc-André Lureau <address@hidden>
> ---
> include/chardev/char.h | 3 +++
> chardev/char.c | 11 +++++++++++
> 2 files changed, 14 insertions(+)
>
> diff --git a/include/chardev/char.h b/include/chardev/char.h
> index 7becd8c80c..014566c3de 100644
> --- a/include/chardev/char.h
> +++ b/include/chardev/char.h
> @@ -47,6 +47,9 @@ typedef enum {
> QEMU_CHAR_FEATURE_FD_PASS,
> /* Whether replay or record mode is enabled */
> QEMU_CHAR_FEATURE_REPLAY,
> + /* Whether the gcontext can be changed after calling
> + * qemu_chr_be_update_read_handlers() */
> + QEMU_CHAR_FEATURE_GCONTEXT,
>
> QEMU_CHAR_FEATURE_LAST,
> } ChardevFeature;
> diff --git a/chardev/char.c b/chardev/char.c
> index e115166995..fa1b74e0d9 100644
> --- a/chardev/char.c
> +++ b/chardev/char.c
> @@ -196,6 +196,8 @@ void qemu_chr_be_update_read_handlers(Chardev *s,
> s->gcontext = context;
> if (cc->chr_update_read_handler) {
> cc->chr_update_read_handler(s);
> + } else if (s->gcontext) {
> + error_report("switching context isn't supported by this chardev");
> }
> }
>
> @@ -240,6 +242,15 @@ static void char_init(Object *obj)
>
> chr->logfd = -1;
> qemu_mutex_init(&chr->chr_write_lock);
> +
> + /*
> + * Assume if chr_update_read_handler is implemented it will
> + * take the updated gcontext into account.
> + */
> + if (CHARDEV_GET_CLASS(chr)->chr_update_read_handler) {
> + qemu_chr_set_feature(chr, QEMU_CHAR_FEATURE_GCONTEXT);
> + }
> +
> }
>
> static int null_chr_write(Chardev *chr, const uint8_t *buf, int len)
> --
> 2.19.0.271.gfe8321ec05
>
Regards,
--
Peter Xu
- [Qemu-devel] [PATCH 0/6] monitor: misc fixes, Marc-André Lureau, 2018/10/09
- [Qemu-devel] [PATCH 1/6] monitor: inline ambiguous helper functions, Marc-André Lureau, 2018/10/09
- [Qemu-devel] [PATCH 2/6] monitor: accept chardev input from iothread, Marc-André Lureau, 2018/10/09
- [Qemu-devel] [PATCH 4/6] monitor: check if chardev can switch gcontext for OOB, Marc-André Lureau, 2018/10/09
- [Qemu-devel] [PATCH 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag, Marc-André Lureau, 2018/10/09
- Re: [Qemu-devel] [PATCH 3/6] char: add a QEMU_CHAR_FEATURE_GCONTEXT flag,
Peter Xu <=
- [Qemu-devel] [PATCH 5/6] monitor: prevent inserting new monitors after cleanup, Marc-André Lureau, 2018/10/09
- [Qemu-devel] [PATCH 6/6] monitor: avoid potential dead-lock when cleaning up, Marc-André Lureau, 2018/10/09