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

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

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 f4c6c0fdb61b0e9198d919cb4056b2961758e3fd
baseline version:
 ovmf                 74bbe31b8d485da26ec7ffad5e78b8384a9eb9a5

Last test of basis    66938  2016-08-08 09:48:59 Z    0 days
Testing same since    66940  2016-08-08 18:19:52 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
  Star Zeng <star.zeng@xxxxxxxxx>

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 f4c6c0fdb61b0e9198d919cb4056b2961758e3fd
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Aug 5 11:07:19 2016 +0800

    ShellPkg SmbiosView: Show "SocketDesignation" instead of "Socket" for Type 4
    
    It is to make the info shown more aligned with SMBIOS spec.
    
    Cc: Amy Chan <amy.chan@xxxxxxxxx>
    Cc: Ruiyu Ni <ruiyu.ni@xxxxxxxxx>
    Cc: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jaben Carsey <jaben.carsey@xxxxxxxxx>
    Reviewed-by: Amy Chan <amy.chan@xxxxxxxxx>

commit c9f297559be5fd60aefda24b18e77a4208c8dede
Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
Date:   Thu Aug 4 10:39:29 2016 +0200

    BaseTools X64: fold PLT relocations into simple relative references
    
    For X64/GCC, we use position independent code with hidden visibility
    to inform the compiler that symbol references are never resolved at
    runtime, which removes the need for PLTs and GOTs. However, in some
    cases, GCC has been reported to still emit PLT based relocations, which
    we need to handle in the ELF to PE/COFF perform by GenFw.
    
    Unlike GOT based relocations, which are non-trivial to handle since the
    indirections in the code can not be fixed up easily (although relocation
    types exist for X64 that annotate relocation targets as suitable for
    relaxation), PLT relocations simply point to jump targets, and we can
    relax such relocations by resolving them using the symbol directly rather
    than via a PLT entry that does nothing more than tail call the function
    we already know it is going to call (since all symbol references are
    resolved in the same module).
    
    So handle R_X86_64_PLT32 as a R_X86_64_PC32 relocation.
    
    Suggested-by: Steven Shi <steven.shi@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

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