[Xen-devel] [ovmf baseline-only test] 71166: all pass

[Platform Team regression test user <citrix-osstest@xxxxxxxxxxxxxx>]

This run is configured for baseline tests only.

flight 71166 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/71166/

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 c137d95081690d4877fbeb5f1856972e84ac32f2
baseline version:
 ovmf                 59a36f21ac2b4d5e402096a65226e102e8398f45

Last test of basis    71165  2017-04-08 08:46:58 Z    1 days
Testing same since    71166  2017-04-09 07:16:55 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>

jobs:
 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    


------------------------------------------------------------
sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at
    http://osstest.xs.citrite.net/~osstest/testlogs/logs

Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary


Push not applicable.

------------------------------------------------------------
commit c137d95081690d4877fbeb5f1856972e84ac32f2
Author: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
Date:   Fri Apr 7 18:25:58 2017 +1200

    OvmfPkg/QemuVideoDxe: VMWare SVGA device support
    
    In addition to the QXL, Cirrus, etc. VGA adapters, Qemu also implements
    a basic version of VMWare's SVGA display device. Drivers for this
    device exist for some guest OSes which do not support Qemu's other
    display adapters, so supporting it in OVMF is useful in conjunction
    with those OSes.
    
    This change adds support for the SVGA device's framebuffer to
    QemuVideoDxe's graphics output protocol implementation, based on
    VMWare's documentation. The most basic initialisation, framebuffer
    layout query, and mode setting operations are implemented.
    
    The device relies on port-based 32-bit I/O, unfortunately on misaligned
    addresses. This limits the driver's support to the x86 family of
    platforms.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 05a5379458725234de8a05780fcb5da2c12680e4
Author: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
Date:   Fri Apr 7 18:25:57 2017 +1200

    OvmfPkg/QemuVideoDxe: Helper functions for unaligned port I/O.
    
    The VMWare SVGA display device implemented by Qemu (-vga vmware) uses
    an I/O-type BAR which is laid out such that some register offsets are
    not aligned to the read/write width with which they are expected to be
    accessed. (The register value port has an offset of 1 and requires
    32 bit wide read/write access.)
    
    The EFI_PCI_IO_PROTOCOL's Io.Read/Io.Write functions do not support
    such unaligned I/O.
    
    Before a driver for this device can be added to QemuVideoDxe, helper
    functions for unaligned I/O are therefore required. This adds the
    functions UnalignedIoWrite32 and UnalignedIoRead32, based on IoLib's
    IoWrite32 and IoRead32, for the Ia32 and X64 architectures. Port I/O
    requires inline assembly, so implementations are provided for the GCC,
    ICC, and Microsoft compiler families. Such I/O is not possible on other
    architectures, a dummy (ASSERT()ing) implementation is therefore
    provided to satisfy the linker.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Suggested-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 9bcca53fe466cdff397578328d9d87d257aba493
Author: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
Date:   Fri Apr 7 18:25:56 2017 +1200

    OvmfPkg: VMWare SVGA display device register definitions
    
    This adds a header file defining symbolic constants for the VMWare SVGA
    virtual display device in preparation for supporting it in
    QemuVideoDxe.
    
    It is mostly an extract of the file lib/vmware/svga_reg.h from commit
    329dd537456f93a806841ec8a8213aed11395def of VMWare's vmware-svga
    repository at git://git.code.sf.net/p/vmware-svga/git (See also
    http://vmware-svga.sourceforge.net/ )
    
    Only the bare essentials necessary for initialisation, modesetting and
    framebuffer access have been kept from the original file; macro names
    have been prefixed with VMWARE_SVGA_ instead of SVGA2_, and the enum
    definition has been adapted to comply with EDK2 naming conventions.
    
    The original file was released by VMWare under the MIT license, this
    has been retained.
    
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Phil Dennis-Jordan <phil@xxxxxxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel