• Kevin Wolf's avatar
    make check-block: Use default cache modes · d9323e9b
    Kevin Wolf authored
    When qemu-iotests only gave a choice between cache=none and
    cache=writethrough, we picked cache=none because it was the option that
    would complete the test in finite time. Some tests could only work for
    one of the two options and would be skipped with cache=none, but that
    was an acceptable trade-off at the time.
    Today, however, qemu-iotests is a bit more flexible than that and you
    can specify any of the cache modes supported by qemu. The default is
    writeback, like in qemu, which is fast and (unlike cache=none) compatible
    with any host filesystem. Test cases that have specific requirements for
    the cache mode can also specify a different default.
    In order to get a fast test run that works everywhere and doesn't skip
    tests that need a different cache mode, not specifying any cache mode
    and instead relying on the default is the best we can do today.
    Signed-off-by: default avatarKevin Wolf <kwolf@redhat.com>
    Reviewed-by: default avatarMarkus Armbruster <armbru@redhat.com>
    Message-id: 1412076430-11623-2-git-send-email-kwolf@redhat.com
    Signed-off-by: default avatarStefan Hajnoczi <stefanha@redhat.com>
qemu-iotests-quick.sh 87 Bytes