From: Kevin Wolf <kwolf@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: Supriya Kannery <supriyak@linux.vnet.ibm.com>,
Stefan Hajnoczi <stefanha@gmail.com>,
Jeff Cody <jcody@redhat.com>,
qemu-devel@nongnu.org, Luiz Capitulino <lcapitulino@redhat.com>,
Christoph Hellwig <hch@lst.de>
Subject: Re: [Qemu-devel] [RFC Patch 3/7]Qemu: Cmd "block_set_hostcache" for dynamic cache change
Date: Thu, 02 Feb 2012 11:14:30 +0100 [thread overview]
Message-ID: <4F2A6206.60309@redhat.com> (raw)
In-Reply-To: <4F29D42C.8090203@linux.vnet.ibm.com>
Am 02.02.2012 01:09, schrieb Michael Roth:
> On 01/31/2012 09:06 PM, Supriya Kannery wrote:
>> New command "block_set_hostcache" added for dynamically changing
>> host pagecache setting of a block device.
>>
>> Usage:
>> block_set_hostcache<device> <option>
>> <device> = block device
>> <option> = on/off
>>
>> Example:
>> (qemu) block_set_hostcache ide0-hd0 off
>>
>> Signed-off-by: Supriya Kannery<supriyak@linux.vnet.ibm.com>
>>
>> ---
>> block.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> block.h | 2 ++
>> blockdev.c | 26 ++++++++++++++++++++++++++
>> blockdev.h | 2 ++
>> hmp-commands.hx | 14 ++++++++++++++
>> qmp-commands.hx | 27 +++++++++++++++++++++++++++
>> 6 files changed, 125 insertions(+)
>>
>> Index: qemu/block.c
>> ===================================================================
>> --- qemu.orig/block.c
>> +++ qemu/block.c
>> @@ -808,6 +808,35 @@ unlink_and_fail:
>> return ret;
>> }
>>
>> +int bdrv_reopen(BlockDriverState *bs, int bdrv_flags)
>> +{
>> + BlockDriver *drv = bs->drv;
>> + int ret = 0, open_flags;
>> +
>> + /* Quiesce IO for the given block device */
>> + qemu_aio_flush();
>> + ret = bdrv_flush(bs);
>> + if (ret != 0) {
>> + qerror_report(QERR_DATA_SYNC_FAILED, bs->device_name);
>> + return ret;
>> + }
>> + open_flags = bs->open_flags;
>> + bdrv_close(bs);
>> +
>> + ret = bdrv_open(bs, bs->filename, bdrv_flags, drv);
>> + if (ret< 0) {
>> + /* Reopen failed. Try to open with original flags */
>> + qerror_report(QERR_REOPEN_FILE_FAILED, bs->filename);
>> + ret = bdrv_open(bs, bs->filename, open_flags, drv);
>> + if (ret< 0) {
>> + /* Reopen failed with orig and modified flags */
>> + abort();
>> + }
>> + }
>> +
>> + return ret;
>> +}
>> +
>> void bdrv_close(BlockDriverState *bs)
>> {
>> if (bs->drv) {
>> @@ -870,6 +899,33 @@ void bdrv_drain_all(void)
>> }
>> }
>>
>> +int bdrv_change_hostcache(BlockDriverState *bs, bool enable_host_cache)
>> +{
>> + int bdrv_flags = bs->open_flags;
>> +
>> + /* set hostcache flags (without changing WCE/flush bits) */
>> + if (enable_host_cache) {
>> + bdrv_flags&= ~BDRV_O_NOCACHE;
>> + } else {
>> + bdrv_flags |= BDRV_O_NOCACHE;
>> + }
>> +
>> + /* If no change in flags, no need to reopen */
>> + if (bdrv_flags == bs->open_flags) {
>> + return 0;
>> + }
>> +
>> + if (bdrv_is_inserted(bs)) {
>> + /* Reopen file with changed set of flags */
>> + bdrv_flags&= ~BDRV_O_CACHE_WB;
>> + return bdrv_reopen(bs, bdrv_flags);
>
> It seems like the real interface we're wanting here is bdrv_set_flags(),
> or something along that line, with the re-opening being more of an
> implementation detail.
>
> For instance, with raw-posix.c:raw_reopen_prepare() we'll end up
> skipping the re-opening completely if fcntl() is sufficient.
It's reopening a BlockDriverState, not necessarily reopening the image
file that backs it.
bdrv_set_flags() would be good name for what this series is doing, but
I've been thinking about adding a way to actually switch the image file
as well. We could need this for implementing external snapshots of
multiple images atomically.
Kevin
next prev parent reply other threads:[~2012-02-02 10:11 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 3:05 [Qemu-devel] [RFC Patch 0/7]Qemu: Dynamic host pagecache change Supriya Kannery
2012-02-01 3:06 ` [Qemu-devel] [RFC Patch 1/7]Qemu: Enhance "info block" to display host cache setting Supriya Kannery
2012-02-08 12:00 ` Luiz Capitulino
2012-02-13 13:19 ` Supriya Kannery
2012-02-01 3:06 ` [Qemu-devel] [RFC Patch 2/7]Qemu: Error classes for file reopen and data sync failure Supriya Kannery
2012-02-07 7:56 ` Stefan Hajnoczi
2012-02-13 13:13 ` Supriya Kannery
2012-02-01 3:06 ` [Qemu-devel] [RFC Patch 3/7]Qemu: Cmd "block_set_hostcache" for dynamic cache change Supriya Kannery
2012-02-02 0:09 ` Michael Roth
2012-02-02 10:14 ` Kevin Wolf [this message]
2012-02-08 12:07 ` Luiz Capitulino
2012-02-13 13:21 ` Supriya Kannery
2012-02-01 3:06 ` [Qemu-devel] [RFC Patch 4/7]Qemu: Framework for reopening image files safely Supriya Kannery
2012-02-07 10:08 ` Stefan Hajnoczi
2012-02-14 13:34 ` Supriya Kannery
2012-02-08 15:07 ` Kevin Wolf
2012-02-13 13:49 ` Supriya Kannery
2012-02-01 3:07 ` [Qemu-devel] [RFC Patch 5/7]Qemu: raw-posix image file reopen Supriya Kannery
2012-02-02 0:15 ` Michael Roth
2012-02-13 13:12 ` Supriya Kannery
2012-02-07 10:17 ` Stefan Hajnoczi
2012-02-14 13:36 ` Supriya Kannery
2012-02-08 14:54 ` Kevin Wolf
2012-02-13 13:28 ` Supriya Kannery
2012-02-01 3:07 ` [Qemu-devel] [RFC Patch 6/7]Qemu: raw-win32 " Supriya Kannery
2012-02-08 15:02 ` Kevin Wolf
2012-02-13 13:29 ` Supriya Kannery
2012-02-01 3:07 ` [Qemu-devel] [RFC Patch 7/7]Qemu: vmdk " Supriya Kannery
2012-02-01 22:41 ` [Qemu-devel] [RFC Patch 0/7]Qemu: Dynamic host pagecache change Eric Blake
2012-02-02 9:12 ` 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=4F2A6206.60309@redhat.com \
--to=kwolf@redhat.com \
--cc=hch@lst.de \
--cc=jcody@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--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).