qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kurz <groug@kaod.org>
To: Ganesh Goudar <ganeshgr@linux.ibm.com>
Cc: Aravinda Prasad <arawinda.p@gmail.com>,
	aik@ozlabs.ru, qemu-devel@nongnu.org, paulus@ozlabs.org,
	qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH v18 1/7] Wrapper function to wait on condition for the main loop mutex
Date: Sun, 5 Jan 2020 16:17:08 +0100	[thread overview]
Message-ID: <20200105161708.6d4711b1@bahia.lan> (raw)
In-Reply-To: <20200102075111.25308-2-ganeshgr@linux.ibm.com>

On Thu,  2 Jan 2020 13:21:05 +0530
Ganesh Goudar <ganeshgr@linux.ibm.com> wrote:

> From: Aravinda Prasad <arawinda.p@gmail.com>
> 
> Introduce a wrapper function to wait on condition for
> the main loop mutex. This function atomically releases
> the main loop mutex and causes the calling thread to
> block on the condition. This wrapper is required because
> qemu_global_mutex is a static variable.
> 
> Signed-off-by: Aravinda Prasad <arawinda.p@gmail.com>
> Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
> Reviewed-by: Greg Kurz <groug@kaod.org>
> ---

This should have your Signed-off-by: tag as well.

>  cpus.c                   | 5 +++++
>  include/qemu/main-loop.h | 8 ++++++++
>  2 files changed, 13 insertions(+)
> 
> diff --git a/cpus.c b/cpus.c
> index b472378b70..79388d2b0f 100644
> --- a/cpus.c
> +++ b/cpus.c
> @@ -1835,6 +1835,11 @@ void qemu_mutex_unlock_iothread(void)
>      qemu_mutex_unlock(&qemu_global_mutex);
>  }
>  
> +void qemu_cond_wait_iothread(QemuCond *cond)
> +{
> +    qemu_cond_wait(cond, &qemu_global_mutex);
> +}
> +
>  static bool all_vcpus_paused(void)
>  {
>      CPUState *cpu;
> diff --git a/include/qemu/main-loop.h b/include/qemu/main-loop.h
> index f6ba78ea73..a6d20b0719 100644
> --- a/include/qemu/main-loop.h
> +++ b/include/qemu/main-loop.h
> @@ -295,6 +295,14 @@ void qemu_mutex_lock_iothread_impl(const char *file, int line);
>   */
>  void qemu_mutex_unlock_iothread(void);
>  
> +/*
> + * qemu_cond_wait_iothread: Wait on condition for the main loop mutex
> + *
> + * This function atomically releases the main loop mutex and causes
> + * the calling thread to block on the condition.
> + */
> +void qemu_cond_wait_iothread(QemuCond *cond);
> +
>  /* internal interfaces */
>  
>  void qemu_fd_register(int fd);



  reply	other threads:[~2020-01-05 15:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02  7:51 [PATCH v18 0/7] target-ppc/spapr: Add FWNMI support in QEMU for PowerKM guests Ganesh Goudar
2020-01-02  7:51 ` [PATCH v18 1/7] Wrapper function to wait on condition for the main loop mutex Ganesh Goudar
2020-01-05 15:17   ` Greg Kurz [this message]
2020-01-07 11:30     ` Ganesh
2020-01-02  7:51 ` [PATCH v18 2/7] ppc: spapr: Introduce FWNMI capability Ganesh Goudar
2020-01-06  9:07   ` Greg Kurz
2020-01-07 11:31     ` Ganesh
2020-01-02  7:51 ` [PATCH v18 3/7] target/ppc: Handle NMI guest exit Ganesh Goudar
2020-01-06  9:45   ` Greg Kurz
2020-01-07 11:32     ` Ganesh
2020-01-02  7:51 ` [PATCH v18 4/7] target/ppc: Build rtas error log upon an MCE Ganesh Goudar
2020-01-02  7:51 ` [PATCH v18 5/7] ppc: spapr: Handle "ibm, nmi-register" and "ibm, nmi-interlock" RTAS calls Ganesh Goudar
2020-01-03  2:19   ` [PATCH v18 5/7] ppc: spapr: Handle "ibm,nmi-register" and "ibm,nmi-interlock" " David Gibson
2020-01-07  6:27     ` Ganesh
2020-01-08  1:04       ` David Gibson
2020-01-08 18:49         ` Ganesh
2020-01-09  1:37           ` David Gibson
2020-01-02  7:51 ` [PATCH v18 6/7] migration: Include migration support for machine check handling Ganesh Goudar
2020-01-03  2:25   ` David Gibson
2020-01-07 11:28     ` Ganesh
2020-01-08  5:45       ` David Gibson
2020-01-02  7:51 ` [PATCH v18 7/7] ppc: spapr: Activate the FWNMI functionality Ganesh Goudar

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=20200105161708.6d4711b1@bahia.lan \
    --to=groug@kaod.org \
    --cc=aik@ozlabs.ru \
    --cc=arawinda.p@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=ganeshgr@linux.ibm.com \
    --cc=paulus@ozlabs.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).