qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Fam Zheng <famz@redhat.com>
Cc: qemu-devel@nongnu.org, stefanha@redhat.com
Subject: Re: [Qemu-devel] [PATCH] qemu-iotests: Use cache=writeback in drive_add
Date: Wed, 13 Nov 2013 14:39:09 +0100	[thread overview]
Message-ID: <20131113133909.GD2633@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1384345671-14866-1-git-send-email-famz@redhat.com>

Am 13.11.2013 um 13:27 hat Fam Zheng geschrieben:
> This will allow running iotests on tmpfs, which is much faster, so we
> can run more tests.
> 
> Signed-off-by: Fam Zheng <famz@redhat.com>
> ---
>  tests/qemu-iotests/iotests.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/qemu-iotests/iotests.py b/tests/qemu-iotests/iotests.py
> index fb10ff4..c29314a 100644
> --- a/tests/qemu-iotests/iotests.py
> +++ b/tests/qemu-iotests/iotests.py
> @@ -96,7 +96,7 @@ class VM(object):
>          '''Add a virtio-blk drive to the VM'''
>          options = ['if=virtio',
>                     'format=%s' % imgfmt,
> -                   'cache=none',
> +                   'cache=writeback',
>                     'file=%s' % path,
>                     'id=drive%d' % self._num_drives]
>          if opts:

Well, in fact any fixed value is wrong here. By default, qemu-iotests is
supposed to use cache=writethrough for everything, and ./check -nocache
should make it cache=none. I think what we really want is a ./check
option that allows specifying any cache option, and then we should make
the scripts honour that option.

Kevin

      reply	other threads:[~2013-11-13 13:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 12:27 [Qemu-devel] [PATCH] qemu-iotests: Use cache=writeback in drive_add Fam Zheng
2013-11-13 13:39 ` Kevin Wolf [this message]

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=20131113133909.GD2633@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).