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

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

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 424a5ec33b3d5a842bff3f4695d0bd709c91a163
baseline version:
 ovmf                 a3a4737051010a94832f7bceaa1fa414d7259da0

Last test of basis    72127  2017-09-19 16:20:35 Z    0 days
Testing same since    72129  2017-09-19 23:49:40 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>

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 424a5ec33b3d5a842bff3f4695d0bd709c91a163
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Fri Sep 15 16:06:02 2017 -0700

    BaseTools/tools_def AARCH64: enable frame pointers for RELEASE builds
    
    Commit 8f0b62a5dac0 ("BaseTools/tools_def AARCH64: enable frame pointers
    for DEBUG builds") removed the -fomit-frame-pointer switch from the CFLAGS
    definitions that are shared between AARCH64 DEBUG and RELEASE builds, and
    moved it to the RELEASE specific ones, so that DEBUG builds can produce a
    backtrace when a crash occurs.
    
    This is actually a useful thing to have for RELEASE builds as well. AArch64
    has 30 general purpose registers, and so the performance hit of having a
    frame pointer is unlikely to be noticeable, nor are the additional 8 bytes
    of stack space likely to present a problem.
    
    So remove -fomit-frame-pointer altogether this time.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 4bbcc285d5f74d34ec40733dde807f5a4f0cdf8c
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Mon Sep 11 17:50:29 2017 +0100

    ArmPkg/PlatformBootManagerLib: process pending capsules
    
    Process any capsule HOBs that were left for us by CapsulePei. This
    involves calling ProcessCapsules() twice, as explained in the comment
    in DxeCapsuleLibFmp [sic].
    
    1) The first call must be before EndOfDxe. The system capsules is processed.
       If device capsule FMP protocols are exposted at this time and device FMP
       capsule has zero EmbeddedDriverCount, the device capsules are processed.
       Each individual capsule result is recorded in capsule record variable.
       System may reset in this function, if reset is required by capsule and
       all capsules are processed.
       If not all capsules are processed, reset will be defered to second call.
    
    2) The second call must be after EndOfDxe and after ConnectAll, so that all
       device capsule FMP protocols are exposed.
       The system capsules are skipped. If the device capsules are NOT processed
       in first call, they are processed here.
       Each individual capsule result is recorded in capsule record variable.
       System may reset in this function, if reset is required by capsule
       processed in first call and second call.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Leif Lindholm <leif.lindholm@xxxxxxxxxx>

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