qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Supriya Kannery <supriyak@linux.vnet.ibm.com>
Cc: qemu-devel@nongnu.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [V3 1/3] Enhance "info block" to display hostcache setting
Date: Mon, 20 Jun 2011 16:23:09 +0200	[thread overview]
Message-ID: <4DFF57CD.3040108@redhat.com> (raw)
In-Reply-To: <20110617163735.2933.67191.sendpatchset@skannery>

Am 17.06.2011 18:37, schrieb Supriya Kannery:
> Enhance "info block" to display hostcache setting for each
> block device.
> 
> Example:
> (qemu) info block
> ide0-hd0: type=hd removable=0 file=../rhel6-32.qcow2 ro=0 drv=qcow2
> encrypted=0
> 
> Enhanced to display "hostcache" setting:
> (qemu) info block
> ide0-hd0: type=hd removable=0 hostcache=true file=../rhel6-32.qcow2 
> ro=0 drv=qcow2 encrypted=0
> 
> Signed-off-by: Supriya Kannery <supriyak@in.ibm.com>
> 
> ---
>  block.c         |   21 +++++++++++++++++----
>  qmp-commands.hx |    2 ++
>  2 files changed, 19 insertions(+), 4 deletions(-)
> 
> Index: qemu/block.c
> ===================================================================
> --- qemu.orig/block.c
> +++ qemu/block.c
> @@ -1694,6 +1694,14 @@ static void bdrv_print_dict(QObject *obj
>          monitor_printf(mon, " locked=%d", qdict_get_bool(bs_dict, "locked"));
>      }
>  
> +	if (qdict_haskey(bs_dict, "open_flags")) {
> +		int open_flags = qdict_get_int(bs_dict, "open_flags");
> +		if (open_flags & BDRV_O_NOCACHE)
> +			monitor_printf(mon, " hostcache=false");
> +		else
> +			monitor_printf(mon, " hostcache=true");

Coding style requires braces.

> +	}
> +
>      if (qdict_haskey(bs_dict, "inserted")) {
>          QDict *qdict = qobject_to_qdict(qdict_get(bs_dict, "inserted"));
>  
> @@ -1730,13 +1738,18 @@ void bdrv_info(Monitor *mon, QObject **r
>          QObject *bs_obj;
>  
>          bs_obj = qobject_from_jsonf("{ 'device': %s, 'type': 'unknown', "
> -                                    "'removable': %i, 'locked': %i }",
> -                                    bs->device_name, bs->removable,
> -                                    bs->locked);
> +									 "'removable': %i, 'locked': %i, "
> +									 "'hostcache': %s }",
> +									 bs->device_name, bs->removable,
> +									 bs->locked,
> +									 (bs->open_flags & BDRV_O_NOCACHE) ?
> +									 "false" : "true");

Don't use tabs.

Kevin

  reply	other threads:[~2011-06-20 14:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-17 16:37 [Qemu-devel] [V3 0/3]block: Dynamically change hostcache setting using new "block_set" command Supriya Kannery
2011-06-17 16:37 ` [Qemu-devel] [V3 1/3] Enhance "info block" to display hostcache setting Supriya Kannery
2011-06-20 14:23   ` Kevin Wolf [this message]
2011-06-22 14:59     ` Supriya Kannery
2011-06-17 16:37 ` [Qemu-devel] [V3 2/3] Error classes for file reopen and device insertion Supriya Kannery
2011-06-20 14:23   ` Kevin Wolf
2011-06-17 16:38 ` [Qemu-devel] [V2 3/3] Command "block_set" for dynamic block params change Supriya Kannery
2011-06-17 17:23   ` [Qemu-devel] [V2 3/3] <Resend> " Supriya Kannery
2011-06-20 14:34   ` [Qemu-devel] [V2 3/3] " Kevin Wolf
2011-06-22 16:09     ` Supriya Kannery
2011-06-27  8:18       ` Kevin Wolf

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=4DFF57CD.3040108@redhat.com \
    --to=kwolf@redhat.com \
    --cc=hch@lst.de \
    --cc=qemu-devel@nongnu.org \
    --cc=supriyak@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).