Andrew de los Reyes 8e93647f05 kvm: set cache type to unsafe if possible, else writeback ...

We try to set the cache type to unsafe, which is a new kvm feature,
else we set the cache type to writeback. The hope is that these cache
types will perform better on the bots, especially in the case of the
guest trying to flush data to disk.

The CL includes code to determine which version of kvm is running, and
the cache type is chosen based on that.

BUG=chromium-os:20305
TEST=trybot

Change-Id: Icf7dbb8f0056a330282ebeb81d0902b3d54f34c5
Reviewed-on: http://gerrit.chromium.org/gerrit/8360
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Andrew de los Reyes <adlr@chromium.org>

2011-09-27 16:30:09 -07:00

..

shflags

Move shflags into crosutils.git

2010-07-13 15:24:54 -07:00

cros_build_lib_unittest.py

Add better support for getting the path to crosutils.

2011-03-30 11:22:17 -07:00

cros_build_lib.py

crosutils: globally replace enter_chroot with cros_sdk

2011-08-19 15:35:32 -07:00

cros_image_common.sh

crosutils: allow factory scripts to be executed in a limited bundle environment

2011-09-18 21:24:11 -07:00

cros_vm_constants.sh

Increase statefulfs_size to accomadate larger stateful partitions.

2010-10-18 10:26:16 -07:00

cros_vm_lib.sh

kvm: set cache type to unsafe if possible, else writeback

2011-09-27 16:30:09 -07:00