mirror of https://github.com/xemu-project/xemu.git
block: Remove BDRV_O_COPY_ON_READ for bs->file
Copy on Read makes sense on the format level where backing files are implemented, but it's not required on the protocol level. While it shouldn't actively break anything to have COR enabled on both layers, needless serialisation and allocation checks may impact performance. Signed-off-by: Kevin Wolf <kwolf@redhat.com> Reviewed-by: Max Reitz <mreitz@redhat.com>
This commit is contained in:
parent
317fc44ef2
commit
5669b44de5
2
block.c
2
block.c
|
@ -793,7 +793,7 @@ static int bdrv_inherited_flags(int flags)
|
||||||
}
|
}
|
||||||
|
|
||||||
/* Clear flags that only apply to the top layer */
|
/* Clear flags that only apply to the top layer */
|
||||||
flags &= ~(BDRV_O_SNAPSHOT | BDRV_O_NO_BACKING);
|
flags &= ~(BDRV_O_SNAPSHOT | BDRV_O_NO_BACKING | BDRV_O_COPY_ON_READ);
|
||||||
|
|
||||||
return flags;
|
return flags;
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue