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,
	Wenchao Xia <xiawenc@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] [PATCH v2 0/2] Add cache mode option to qemu-iotests
Date: Tue, 19 Nov 2013 11:21:22 +0100	[thread overview]
Message-ID: <20131119102122.GB4040@dhcp-200-207.str.redhat.com> (raw)
In-Reply-To: <1384843537-14112-1-git-send-email-famz@redhat.com>

Am 19.11.2013 um 07:45 hat Fam Zheng geschrieben:
> The first patch adds "-c <mode>" option to ./check and convert "-nocache" to an
> alias to "-c none". The mode is used in qemu-io.
> 
> The second patch modifies iotests.py to use the cache mode option in qemu drive
> command line.

Okay, I gave it some testing, too, and it looks like we need some
additional changes. There are some test cases that use:

_unsupported_qemu_io_options --nocache

Which obviously doesn't work any more. We need to replace it by a check
against $CACHEMODE (or, perhaps preferably, even override it
automatically, so that test cases aren't left out just because of the
cache mode)

Test case 026 uses the option of having a 026.out.nocache, which differs
from the normal output. I suspect the correct differentiation is here
between writethrough and writeback modes. And of course, grepping for
'--nocache' to detect the condition doesn't work any more.

Kevin

      parent reply	other threads:[~2013-11-19 10:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-19  6:45 [Qemu-devel] [PATCH v2 0/2] Add cache mode option to qemu-iotests Fam Zheng
2013-11-19  6:45 ` [Qemu-devel] [PATCH v2 1/2] qemu-iotests: Add "-c <cache-mode>" option Fam Zheng
2013-11-19  6:45 ` [Qemu-devel] [PATCH v2 2/2] qemu-iotests: Honour cache mode in iotests.py Fam Zheng
2013-11-19 10:10 ` [Qemu-devel] [PATCH v2 0/2] Add cache mode option to qemu-iotests Kevin Wolf
2013-11-19 10:21 ` 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=20131119102122.GB4040@dhcp-200-207.str.redhat.com \
    --to=kwolf@redhat.com \
    --cc=famz@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=xiawenc@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).