qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Marc-André Lureau" <marcandre.lureau@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Thomas Huth <thuth@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>,
	Yongji Xie <elohimes@gmail.com>
Subject: Re: [Qemu-devel] [PATCH v2 01/16] io: store reference to thread information in the QIOTask struct
Date: Mon, 4 Feb 2019 11:37:57 +0100	[thread overview]
Message-ID: <CAMxuvayRb9_FjR--Y9enzyh40TrkynfyXnx_860xtnkFevNb1Q@mail.gmail.com> (raw)
In-Reply-To: <20190123172740.32452-2-berrange@redhat.com>

On Wed, Jan 23, 2019 at 6:27 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
>
> Currently the struct QIOTaskThreadData is only needed by the worker
> thread, but a subsequent patch will need to access it from another
> context.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>

Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>

> ---
>  io/task.c | 53 ++++++++++++++++++++++++++++-------------------------
>  1 file changed, 28 insertions(+), 25 deletions(-)
>
> diff --git a/io/task.c b/io/task.c
> index 2886a2c1bc..d100a754d3 100644
> --- a/io/task.c
> +++ b/io/task.c
> @@ -24,6 +24,14 @@
>  #include "qemu/thread.h"
>  #include "trace.h"
>
> +struct QIOTaskThreadData {
> +    QIOTaskWorker worker;
> +    gpointer opaque;
> +    GDestroyNotify destroy;
> +    GMainContext *context;
> +};
> +
> +
>  struct QIOTask {
>      Object *source;
>      QIOTaskFunc func;
> @@ -32,6 +40,7 @@ struct QIOTask {
>      Error *err;
>      gpointer result;
>      GDestroyNotify destroyResult;
> +    struct QIOTaskThreadData *thread;
>  };
>
>
> @@ -72,31 +81,23 @@ static void qio_task_free(QIOTask *task)
>  }
>
>
> -struct QIOTaskThreadData {
> -    QIOTask *task;
> -    QIOTaskWorker worker;
> -    gpointer opaque;
> -    GDestroyNotify destroy;
> -    GMainContext *context;
> -};
> -
> -
>  static gboolean qio_task_thread_result(gpointer opaque)
>  {
> -    struct QIOTaskThreadData *data = opaque;
> +    QIOTask *task = opaque;
>
> -    trace_qio_task_thread_result(data->task);
> -    qio_task_complete(data->task);
> +    trace_qio_task_thread_result(task);
> +    qio_task_complete(task);
>
> -    if (data->destroy) {
> -        data->destroy(data->opaque);
> +    if (task->thread->destroy) {
> +        task->thread->destroy(task->thread->opaque);
>      }
>
> -    if (data->context) {
> -        g_main_context_unref(data->context);
> +    if (task->thread->context) {
> +        g_main_context_unref(task->thread->context);
>      }
>
> -    g_free(data);
> +    g_free(task->thread);
> +    task->thread = NULL;
>
>      return FALSE;
>  }
> @@ -104,22 +105,23 @@ static gboolean qio_task_thread_result(gpointer opaque)
>
>  static gpointer qio_task_thread_worker(gpointer opaque)
>  {
> -    struct QIOTaskThreadData *data = opaque;
> +    QIOTask *task = opaque;
>      GSource *idle;
>
> -    trace_qio_task_thread_run(data->task);
> -    data->worker(data->task, data->opaque);
> +    trace_qio_task_thread_run(task);
> +
> +    task->thread->worker(task, task->thread->opaque);
>
>      /* We're running in the background thread, and must only
>       * ever report the task results in the main event loop
>       * thread. So we schedule an idle callback to report
>       * the worker results
>       */
> -    trace_qio_task_thread_exit(data->task);
> +    trace_qio_task_thread_exit(task);
>
>      idle = g_idle_source_new();
> -    g_source_set_callback(idle, qio_task_thread_result, data, NULL);
> -    g_source_attach(idle, data->context);
> +    g_source_set_callback(idle, qio_task_thread_result, task, NULL);
> +    g_source_attach(idle, task->thread->context);
>
>      return NULL;
>  }
> @@ -138,17 +140,18 @@ void qio_task_run_in_thread(QIOTask *task,
>          g_main_context_ref(context);
>      }
>
> -    data->task = task;
>      data->worker = worker;
>      data->opaque = opaque;
>      data->destroy = destroy;
>      data->context = context;
>
> +    task->thread = data;
> +
>      trace_qio_task_thread_start(task, worker, opaque);
>      qemu_thread_create(&thread,
>                         "io-task-worker",
>                         qio_task_thread_worker,
> -                       data,
> +                       task,
>                         QEMU_THREAD_DETACHED);
>  }
>
> --
> 2.20.1
>

  reply	other threads:[~2019-02-04 10:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-23 17:27 [Qemu-devel] [PATCH v2 00/16] chardev: refactoring & many bugfixes related tcp_chr_wait_connected Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 01/16] io: store reference to thread information in the QIOTask struct Daniel P. Berrangé
2019-02-04 10:37   ` Marc-André Lureau [this message]
2019-02-04 10:40     ` Marc-André Lureau
2019-02-04 13:56       ` Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 02/16] io: add qio_task_wait_thread to join with a background thread Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 03/16] chardev: fix validation of options for QMP created chardevs Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 04/16] chardev: forbid 'reconnect' option with server sockets Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 05/16] chardev: forbid 'wait' option with client sockets Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 06/16] chardev: remove many local variables in qemu_chr_parse_socket Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 07/16] chardev: ensure qemu_chr_parse_compat reports missing driver error Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 08/16] chardev: remove unused 'sioc' variable & cleanup paths Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 09/16] chardev: split tcp_chr_wait_connected into two methods Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 10/16] chardev: split up qmp_chardev_open_socket connection code Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 11/16] chardev: use a state machine for socket connection state Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 12/16] chardev: honour the reconnect setting in tcp_chr_wait_connected Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 13/16] chardev: disallow TLS/telnet/websocket with tcp_chr_wait_connected Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 14/16] chardev: fix race with client connections in tcp_chr_wait_connected Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 15/16] tests: expand coverage of socket chardev test Daniel P. Berrangé
2019-01-23 17:27 ` [Qemu-devel] [PATCH v2 16/16] chardev: ensure termios is fully initialized Daniel P. Berrangé
2019-02-04 10:20   ` Marc-André Lureau
2019-02-06 13:45 ` [Qemu-devel] [PATCH v2 00/16] chardev: refactoring & many bugfixes related tcp_chr_wait_connected Marc-André Lureau
2019-02-06 13:56   ` Daniel P. Berrangé
2019-02-06 14:35     ` 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=CAMxuvayRb9_FjR--Y9enzyh40TrkynfyXnx_860xtnkFevNb1Q@mail.gmail.com \
    --to=marcandre.lureau@redhat.com \
    --cc=berrange@redhat.com \
    --cc=elohimes@gmail.com \
    --cc=lvivier@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.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 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).