From: Luiz Capitulino <lcapitulino@redhat.com>
To: benoit.canet@gmail.com
Cc: kwolf@redhat.com, stefanha@linux.vnet.ibm.com,
stefanha@gmail.com, qemu-devel@nongnu.org, pbonzini@redhat.com,
"Benoît Canet" <benoit@irqsave.net>
Subject: Re: [Qemu-devel] [PATCH V4 1/3] block: Add bdrv_are_busy()
Date: Mon, 23 Jul 2012 14:15:01 -0300 [thread overview]
Message-ID: <20120723141501.735465ca@doriath.home> (raw)
In-Reply-To: <1343053380-12133-2-git-send-email-benoit@irqsave.net>
On Mon, 23 Jul 2012 16:22:58 +0200
benoit.canet@gmail.com wrote:
> From: Benoît Canet <benoit@irqsave.net>
>
> bdrv_are_busy will be used to check if any of the bs are in use
> or if one of them have a running block job.
>
> The first user will be qmp_migrate().
>
> Signed-off-by: Benoit Canet <benoit@irqsave.net>
> ---
> block.c | 13 +++++++++++++
> block.h | 2 ++
> 2 files changed, 15 insertions(+)
>
> diff --git a/block.c b/block.c
> index ce7eb8f..bc8f160 100644
> --- a/block.c
> +++ b/block.c
> @@ -4027,6 +4027,19 @@ out:
> return ret;
> }
>
> +int bdrv_are_busy(void)
> +{
> + BlockDriverState *bs;
> +
> + QTAILQ_FOREACH(bs, &bdrv_states, list) {
> + if (bs->job || bdrv_in_use(bs)) {
> + return -EBUSY;
> + }
> + }
IMO, this should return true/false. The name is a bit misleading too, as it
gives the impression that are existing bdrvs are busy. I'd call it
bdrv_any_busy() or bdrv_any_in_use().
> +
> + return 0;
> +}
> +
> void *block_job_create(const BlockJobType *job_type, BlockDriverState *bs,
> int64_t speed, BlockDriverCompletionFunc *cb,
> void *opaque, Error **errp)
> diff --git a/block.h b/block.h
> index c89590d..0a3de2f 100644
> --- a/block.h
> +++ b/block.h
> @@ -337,6 +337,8 @@ void bdrv_disable_copy_on_read(BlockDriverState *bs);
> void bdrv_set_in_use(BlockDriverState *bs, int in_use);
> int bdrv_in_use(BlockDriverState *bs);
>
> +int bdrv_are_busy(void);
> +
> enum BlockAcctType {
> BDRV_ACCT_READ,
> BDRV_ACCT_WRITE,
next prev parent reply other threads:[~2012-07-23 17:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 14:22 [Qemu-devel] [PATCH V4 0/3] Block migration if any of the block device is busy benoit.canet
2012-07-23 14:22 ` [Qemu-devel] [PATCH V4 1/3] block: Add bdrv_are_busy() benoit.canet
2012-07-23 17:15 ` Luiz Capitulino [this message]
2012-07-24 10:10 ` Benoît Canet
2012-07-24 12:55 ` Luiz Capitulino
2012-07-24 13:29 ` Kevin Wolf
2012-07-24 14:37 ` Benoît Canet
2012-07-24 14:42 ` Kevin Wolf
2012-07-23 14:22 ` [Qemu-devel] [PATCH V4 2/3] qerror: Add error telling that block dev usage prevents migration benoit.canet
2012-07-23 17:09 ` Luiz Capitulino
2012-07-23 14:23 ` [Qemu-devel] [PATCH V4 3/3] migration: block migration when any of the block device is busy benoit.canet
2012-07-23 14:58 ` [Qemu-devel] [PATCH V4 0/3] Block migration if " Stefan Hajnoczi
2012-07-24 9:52 ` Kevin Wolf
2012-07-24 10:04 ` Stefan Hajnoczi
2012-07-24 10:19 ` Kevin Wolf
2012-07-24 11:12 ` Paolo Bonzini
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=20120723141501.735465ca@doriath.home \
--to=lcapitulino@redhat.com \
--cc=benoit.canet@gmail.com \
--cc=benoit@irqsave.net \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=stefanha@linux.vnet.ibm.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).