[Xen-devel] [ovmf baseline-only test] 75282: trouble: blocked/broken

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

This run is configured for baseline tests only.

flight 75282 ovmf real [real]
http://osstest.xensource.com/osstest/logs/75282/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-xsm                 <job status>                 broken
 build-i386                      <job status>                 broken
 build-amd64-pvops               <job status>                 broken
 build-i386-xsm                  <job status>                 broken
 build-amd64                     <job status>                 broken
 build-i386-pvops                <job status>                 broken

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-xl-qemuu-ovmf-amd64  1 build-check(1)             blocked n/a
 build-amd64-libvirt           1 build-check(1)               blocked  n/a
 test-amd64-i386-xl-qemuu-ovmf-amd64  1 build-check(1)              blocked n/a
 build-i386-libvirt            1 build-check(1)               blocked  n/a
 build-i386                    4 host-install(4)       broken baseline untested
 build-i386-pvops              4 host-install(4)       broken baseline untested
 build-i386-xsm                4 host-install(4)       broken baseline untested
 build-amd64-xsm               4 host-install(4)       broken baseline untested
 build-amd64-pvops             4 host-install(4)       broken baseline untested
 build-amd64                   4 host-install(4)       broken baseline untested

version targeted for testing:
 ovmf                 a364928195e911c2650fcae6bd34cfd501df1f57
baseline version:
 ovmf                 60eb6c6d2e01e8d44d29740b006df1fc7e74ab21

Last test of basis    75280  2018-09-24 21:21:07 Z    0 days
Testing same since    75282  2018-09-25 02:50:20 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@xxxxxxxxxx>
  Liming Gao <liming.gao@xxxxxxxxx>

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


------------------------------------------------------------
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.xensource.com/osstest/logs

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

broken-job build-amd64-xsm broken
broken-job build-i386 broken
broken-job build-amd64-pvops broken
broken-job build-i386-xsm broken
broken-job build-amd64 broken
broken-job build-i386-pvops broken
broken-step build-i386 host-install(4)
broken-step build-i386-pvops host-install(4)
broken-step build-i386-xsm host-install(4)
broken-step build-amd64-xsm host-install(4)
broken-step build-amd64-pvops host-install(4)
broken-step build-amd64 host-install(4)

Push not applicable.

------------------------------------------------------------
commit a364928195e911c2650fcae6bd34cfd501df1f57
Author: Liming Gao <liming.gao@xxxxxxxxx>
Date:   Fri Sep 21 08:56:01 2018 +0800

    UefiCpuPkg PiSmmCpuDxeSmm: Update SmiEntry function run the same position
    
    BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1191
    
    Before commit e21e355e2ca7fefb15b4df7078f995d3fb9c2b89, jmp _SmiHandler
    is commented. And below code, ASM_PFX(CpuSmmDebugEntry) is moved into rax,
    then call it. But, this code doesn't work in XCODE5 tool chain. Because 
XCODE5
    doesn't generated the absolute address in the EFI image. So, rax stores the
    relative address. Once this logic is moved to another place, it will not 
work.
    ;   jmp     _SmiHandler                 ; instruction is not needed
    ...
        mov     rax, ASM_PFX(CpuSmmDebugEntry)
        call    rax
    
    Commit e21e355e2ca7fefb15b4df7078f995d3fb9c2b89 is to support XCODE5.
    One tricky way is selected to fix it. Although SmiEntry logic is copied to
    another place and run, but here jmp _SmiHandler is enabled to jmp the 
original
    code place, then call ASM_PFX(CpuSmmDebugEntry) with the relative address.
        mov     rax, strict qword 0         ;   mov     rax, _SmiHandler
    _SmiHandlerAbsAddr:
        jmp     rax
    ...
        call    ASM_PFX(CpuSmmDebugEntry)
    
    Now, BZ 1191 raises the issue that SmiHandler should run in the copied 
address,
    can't run in the common address. So, jmp _SmiHandler is required to be 
removed,
    the code is kept to run in copied address. And, the relative address is
    requried to be fixed up to the absolute address. The necessary changes 
should
    not affect the behavior of platforms that already consume PiSmmCpuDxeSmm.
    OVMF SMM boot to shell with VS2017, GCC5 and XCODE5 tool chain has been 
verified.
    ...
        mov     rax, strict qword 0         ;   call    
ASM_PFX(CpuSmmDebugEntry)
    CpuSmmDebugEntryAbsAddr:
        call    rax
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Eric Dong <eric.dong@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Tested-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

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