Define CAN_BE_ZONED=1 in block/005, block/006, block/010, block/011,
block/016, block/017, block/020, block/021 and block/023 as all these
tests should execute without any problem against null_blk with zoned
mode enabled or zoned block devices specified in TEST_DEVS.
Signed-off-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
DESCRIPTION="switch schedulers while doing IO"
TIMED=1
+CAN_BE_ZONED=1
requires() {
_have_fio
DESCRIPTION="run null-blk in blocking mode"
TIMED=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk && _have_module_param null_blk blocking && _have_fio
DESCRIPTION="run I/O on null_blk with shared and non-shared tags"
TIMED=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk && _have_module_param null_blk shared_tags && _have_fio
DESCRIPTION="disable PCI device while doing I/O"
TIMED=1
+CAN_BE_ZONED=1
requires() {
_have_fio && _have_program setpci
DESCRIPTION="send a signal to a process waiting on a frozen queue"
QUICK=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk
DESCRIPTION="do I/O and check the inflight counter"
QUICK=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk
DESCRIPTION="run null-blk on different schedulers with only one hardware tag"
QUICK=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk && _have_fio
DESCRIPTION="read/write nr_requests on null-blk with different schedulers"
QUICK=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk
DESCRIPTION="do I/O on all null_blk queue modes"
QUICK=1
+CAN_BE_ZONED=1
requires() {
_have_null_blk