[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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



This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 7dc7c7435e9030ad07ad7bc7d136a3997bd0b182
baseline version:
 ovmf                 77ca824c652443bdf3edaa0bb109fd8225a71cd3

Last test of basis    74741  2018-05-24 21:52:05 Z    2 days
Testing same since    74748  2018-05-26 04:52:45 Z    1 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Eric Dong <eric.dong@xxxxxxxxx>
  Laszlo Ersek <lersek@xxxxxxxxxx>
  Marvin Haeuser <Marvin.Haeuser@xxxxxxxxxxx>
  Marvin Häuser <Marvin.Haeuser@xxxxxxxxxxx>

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 7dc7c7435e9030ad07ad7bc7d136a3997bd0b182
Author: Marvin Häuser <Marvin.Haeuser@xxxxxxxxxxx>
Date:   Thu May 17 12:43:30 2018 +0000

    EmulatorPkg/SmbiosLib: Declare the correct library class.
    
    Currently, SmbiosLib declares the PcdLib library class. Update the
    declaration to declare SmbiosLib.
    
    V2:
      - Do not change the copyright date as requested.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Marvin Haeuser <Marvin.Haeuser@xxxxxxxxxxx>
    Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>

commit 5685a243b6f85113591f4bac6cb8ecaa1376094e
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 4 16:40:52 2018 +0200

    OvmfPkg/Virtio10Dxe: convert to PciCapLib
    
    Replace the manual capability list parsing in OvmfPkg/Virtio10Dxe with
    PciCapLib and PciCapPciIoLib API calls.
    
    The VIRTIO_PCI_CAP_LINK structure type is now superfluous. (Well, it
    always has been; we should have used EFI_PCI_CAPABILITY_HDR.)
    
    Also, EFI_PCI_CAPABILITY_VENDOR_HDR is now included at the front of
    VIRTIO_PCI_CAP. No driver other than Virtio10Dxe relies on VIRTIO_PCI_CAP.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 3815101ff854459e74a18571475c1d9ffee6af91
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 4 12:00:00 2018 +0200

    OvmfPkg/PciHotPlugInitDxe: convert to PciCapLib
    
    Replace the manual capability list parsing in OvmfPkg/PciHotPlugInitDxe
    with PciCapLib and PciCapPciSegmentLib API calls.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 65cefddcdecec044f97ec4850cb27379a1a7788a
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 4 10:09:20 2018 +0200

    ArmVirtPkg: resolve PciCapLib, PciCapPciSegmentLib, PciCapPciIoLib
    
    Resolve the PciCapLib, PciCapPciSegmentLib, and PciCapPciIoLib classes to
    their single respective instances under OvmfPkg. Later patches will use
    those lib classes in OvmfPkg drivers, some of which are included in
    ArmVirt platforms.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit e9b2cf7bf015d1f76934a9702237cdb08ea2861c
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 4 10:06:08 2018 +0200

    OvmfPkg: resolve PciCapLib, PciCapPciSegmentLib, PciCapPciIoLib
    
    Resolve the PciCapLib, PciCapPciSegmentLib, and PciCapPciIoLib classes to
    their single respective instances. Later patches will use these lib
    classes in OvmfPkg drivers.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 02b9a8343ffce442195ae8569b4a35424242e67e
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sat Apr 28 23:23:10 2018 +0200

    OvmfPkg: introduce PciCapPciIoLib
    
    Add a library class, and a UEFI_DRIVER lib instance, that are layered on
    top of PciCapLib, and allow clients to plug an EFI_PCI_IO_PROTOCOL backend
    into PciCapLib, for config space access.
    
    (Side note:
    
    Although the UEFI spec says that EFI_PCI_IO_PROTOCOL_CONFIG() returns
    EFI_UNSUPPORTED if "[t]he address range specified by Offset, Width, and
    Count is not valid for the PCI configuration header of the PCI
    controller", this patch doesn't directly document the EFI_UNSUPPORTED
    error code, for ProtoDevTransferConfig() and its callers
    ProtoDevReadConfig() and ProtoDevWriteConfig(). Instead, the patch refers
    to "unspecified error codes". The reason is that in edk2, the
    PciIoConfigRead() and PciIoConfigWrite() functions [1] can also return
    EFI_INVALID_PARAMETER for the above situation.
    
    Namely, PciIoConfigRead() and PciIoConfigWrite() first call
    PciIoVerifyConfigAccess(), which indeed produces the standard
    EFI_UNSUPPORTED error code, if the device's config space is exceeded.
    However, if PciIoVerifyConfigAccess() passes, and we reach
    RootBridgeIoPciRead() and RootBridgeIoPciWrite() [2], then
    RootBridgeIoCheckParameter() can still fail, e.g. if the root bridge
    doesn't support extended config space (see commit 014b472053ae3).
    
    For all kinds of Limit violations in IO, MMIO, and config space,
    RootBridgeIoCheckParameter() returns EFI_INVALID_PARAMETER, not
    EFI_UNSUPPORTED. That error code is then propagated up to, and out of,
    PciIoConfigRead() and PciIoConfigWrite().
    
    [1] MdeModulePkg/Bus/Pci/PciBusDxe/PciIo.c
    [2] MdeModulePkg/Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c
    )
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 6a744d40d0c707b43202ae9b6a1d6ae89f6f864b
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sat Apr 28 23:22:59 2018 +0200

    OvmfPkg: introduce PciCapPciSegmentLib
    
    Add a library class, and a BASE lib instance, that are layered on top of
    PciCapLib, and allow clients to plug a PciSegmentLib backend into
    PciCapLib, for config space access.
    
    (Side note:
    
    The "MaxDomain" parameter is provided because, in practice, platforms
    exist where a PCI Express device may show up on a root bridge such that
    the root bridge doesn't support access to extended config space. Earlier
    the same issue was handled for MdeModulePkg/PciHostBridgeDxe in commit
    014b472053ae3. However, that solution does not apply to the PciSegmentLib
    class, because:
    
    (1) The config space accessor functions of the PciSegmentLib class, such
        as PciSegmentReadBuffer(), have no way of informing the caller whether
        access to extended config space actually succeeds.
    
        (For example, in the UefiPciSegmentLibPciRootBridgeIo instace, which
        could in theory benefit from commit 014b472053ae3, the
        EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL.Pci.Read() status code is explicitly
        ignored, because there's no way for the lib instance to propagate it
        to the PciSegmentLib caller. If the
        EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL.Pci.Read() call fails, then
        DxePciSegmentLibPciRootBridgeIoReadWorker() returns Data with
        indeterminate value.)
    
    (2) There is no *general* way for any firmware platform to provide, or
        use, a PciSegmentLib instance in which access to extended config space
        always succeeds.
    
    In brief, on a platform where config space may be limited to 256 bytes,
    access to extended config space through PciSegmentLib may invoke undefined
    behavior; therefore PciCapPciSegmentLib must give platforms a way to
    prevent such access.)
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 392a31467f4164423ae459bf28b39f282bb48e98
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Sat Apr 28 23:22:11 2018 +0200

    OvmfPkg: introduce PciCapLib
    
    Add a library class, and a BASE lib instance, to work more easily with PCI
    capabilities in PCI config space. Functions are provided to parse
    capabilities lists, and to locate, describe, read and write capabilities.
    PCI config space access is abstracted away.
    
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Suggested-by: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

commit 4b8552d794e7b17a6627e0f752fd298e8bcb2587
Author: Eric Dong <eric.dong@xxxxxxxxx>
Date:   Tue May 22 13:47:16 2018 +0800

    SecurityPkg/TcgStorage*Lib.h: Fix ECC reported issues.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Eric Dong <eric.dong@xxxxxxxxx>
    Reviewed-by: Dandan Bi <dandan.bi@xxxxxxxxx>

commit bc623a1125601227072ee5412018756bb98a1117
Author: Eric Dong <eric.dong@xxxxxxxxx>
Date:   Tue May 22 13:46:42 2018 +0800

    MdePkg/TcgStorage*.h: Fixed ECC reported issues.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Eric Dong <eric.dong@xxxxxxxxx>
    Reviewed-by: Dandan Bi <dandan.bi@xxxxxxxxx>

commit cbf00651eda6818ca3c76115b8a18e3f6b23eef4
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Fri May 18 19:20:32 2018 +0200

    BaseTools/tools_def: add "-fno-unwind-tables" to GCC_AARCH64_CC_FLAGS
    
    The ElfConvert routines in GenFw don't handle the ".eh_frame" ELF section
    emitted by gcc. For this reason, Leif disabled the generation of that
    section for AARCH64 with "-fno-asynchronous-unwind-tables" in commit
    28e80befa4fe [1], and Ard did the same for IA32 and X64 in commit
    26ecc55c027d [2]. (The CLANG38 toolchain received the same flag at its
    inception, in commit 6f756db5ea05 [3].)
    
    However, ".eh_frame" is back now; in upstream gcc commit 9cbee213b579 [4]
    (part of tag "gcc-8_1_0-release"), both "-fasynchronous-unwind-tables" and
    "-funwind-tables" were made the default for AARCH64. (The patch author
    described the effects on the gcc mailing list [5].) We have to counter the
    latter flag with "-fno-unwind-tables", otherwise GenFw chokes on
    ".eh_frame" again (triggered for example on Fedora 28).
    
    "-f[no-]unwind-tables" goes back to at least gcc-4.4 [6], so it's safe to
    add to GCC_AARCH64_CC_FLAGS.
    
    [1] https://github.com/tianocore/edk2/commit/28e80befa4fe
    [2] https://github.com/tianocore/edk2/commit/26ecc55c027d
    [3] https://github.com/tianocore/edk2/commit/6f756db5ea05
    [4] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=9cbee213b579
    [5] 
http://mid.mail-archive.com/7b28c03a-c032-6cec-c127-1c12cbe98eeb@xxxxxxxxxxxx
    [6] https://gcc.gnu.org/onlinedocs/gcc-4.4.7/gcc/Code-Gen-Options.html
    
    Cc: "Danilo C. L. de Paula" <ddepaula@xxxxxxxxxx>
    Cc: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Cc: Cole Robinson <crobinso@xxxxxxxxxx>
    Cc: Gerd Hoffmann <kraxel@xxxxxxxxxx>
    Cc: Leif Lindholm <leif.lindholm@xxxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Paolo Bonzini <pbonzini@xxxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Reported-by: "Danilo C. L. de Paula" <ddepaula@xxxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.