1. 27 9月, 2018 1 次提交
    • G
      display/edid: add edid generator to qemu. · 72d277a7
      Gerd Hoffmann 提交于
      EDID is a metadata format to describe monitors.  On physical hardware
      the monitor has an eeprom with that data block which can be read over
      i2c bus.
      
      On a linux system you can usually find the EDID data block in
      /sys/class/drm/$card/$connector/edid.  xorg ships a edid-decode utility
      which you can use to turn the blob into readable form.
      
      I think it would be a good idea to use EDID for virtual displays too.
      Needs changes in both qemu and guest kms drivers.  This patch is the
      first step, it adds an generator for EDID blobs to qemu.  Comes with a
      qemu-edid test tool included.
      
      With EDID we can pass more information to the guest.  Names and serial
      numbers, so the guests display configuration has no boring "Unknown
      Monitor".  List of video modes.  Display resolution, pretty important
      in case we want add HiDPI support some day.
      Signed-off-by: NGerd Hoffmann <kraxel@redhat.com>
      Message-id: 20180925075646.25114-2-kraxel@redhat.com
      72d277a7
  2. 25 9月, 2018 1 次提交
  3. 24 9月, 2018 1 次提交
  4. 28 8月, 2018 3 次提交
  5. 27 8月, 2018 1 次提交
  6. 25 8月, 2018 1 次提交
  7. 24 8月, 2018 5 次提交
  8. 23 8月, 2018 1 次提交
  9. 20 8月, 2018 2 次提交
  10. 17 8月, 2018 2 次提交
  11. 16 8月, 2018 1 次提交
  12. 16 7月, 2018 1 次提交
  13. 05 7月, 2018 2 次提交
    • A
      travis: add gcovr summary for GCOV build · 0708e647
      Alex Bennée 提交于
      This gives a more useful summary, sorted by descending % coverage,
      after the tests have run. The final numbers will give an idea if our
      coverage is getting better or worse.
      
      To keep the width sane we need to post process the file that the old
      gcovr tool generates. This is done with a mix of sed, awk and column
      in the scripts/coverage-summary.sh script.
      
      As quite a lot of lines don't get covered at all we filter out all the
      0% lines. If the file doesn't appear it is not being exercised.
      Signed-off-by: NAlex Bennée <alex.bennee@linaro.org>
      Reviewed-by: NDaniel P. Berrangé <berrange@redhat.com>
      0708e647
    • A
      block: Add blklogwrites · bfcc224e
      Aapo Vienamo 提交于
      Implements a block device write logging system, similar to Linux kernel
      device mapper dm-log-writes. The write operations that are performed
      on a block device are logged to a file or another block device. The
      write log format is identical to the dm-log-writes format. Currently,
      log markers are not supported.
      
      This functionality can be used for crash consistency and fs consistency
      testing. By implementing it in qemu, tests utilizing write logs can be
      be used to test non-Linux drivers and older kernels.
      
      The driver accepts an optional parameter to set the sector size used
      for logging. This makes the driver require all requests to be aligned
      to this sector size and also makes offsets and sizes of writes in the
      log metadata to be expressed in terms of this value (the log format has
      a granularity of one sector for offsets and sizes). This allows
      accurate logging of writes to guest block devices that have unusual
      sector sizes.
      
      The implementation is based on the blkverify and blkdebug block
      drivers.
      Signed-off-by: NAapo Vienamo <aapo@tuxera.com>
      Signed-off-by: NAri Sundholm <ari@tuxera.com>
      Signed-off-by: NKevin Wolf <kwolf@redhat.com>
      bfcc224e
  14. 03 7月, 2018 1 次提交
  15. 28 6月, 2018 1 次提交
  16. 27 6月, 2018 2 次提交
  17. 22 6月, 2018 2 次提交
  18. 21 6月, 2018 8 次提交
  19. 18 6月, 2018 1 次提交
  20. 15 6月, 2018 1 次提交
  21. 12 6月, 2018 2 次提交