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

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



This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 ec16deeac90e4b8014394be58a229f6aa8c493af
baseline version:
 ovmf                 28b3a713b66998a8be3e8558eb85f18699e15b2e

Last test of basis    68058  2016-11-18 00:51:36 Z    0 days
Testing same since    68059  2016-11-18 06:54:09 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Giri P Mudusuru <giri.p.mudusuru@xxxxxxxxx>
  Hao Wu <hao.a.wu@xxxxxxxxx>
  Jeff Fan <jeff.fan@xxxxxxxxx>
  Maurice Ma <maurice.ma@xxxxxxxxx>
  Michael Kinney <michael.d.kinney@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 ec16deeac90e4b8014394be58a229f6aa8c493af
Author: Jeff Fan <jeff.fan@xxxxxxxxx>
Date:   Tue Nov 15 16:29:22 2016 +0800

    UefiCpuPkg/SecCore: Correct print format for stack information
    
    v2:
      Per Laszlo and Andrew's comments at
        https://lists.01.org/pipermail/edk2-devel/2016-November/004759.html
      SecCoreData->StackBase is VOID * type. We should use %p to dump VOID * 
type.
      SecCoreData->StackSize is UINTN type, but %x only could print unsinged-int
      type. We will cast it to UINT32 firstly and then use %x to print it.
    
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jeff Fan <jeff.fan@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>

commit 5c88af795dadb81c9fe43af813b7b6d69bc5e0e4
Author: Jeff Fan <jeff.fan@xxxxxxxxx>
Date:   Wed Nov 16 22:25:56 2016 +0800

    MdeModulePkg/PiSmmCpuDxeSmm: Check RegisterCpuInterruptHandler status
    
    Once platform selects the incorrect instance, the caller could know it from
    return status and ASSERT().
    
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jeff Fan <jeff.fan@xxxxxxxxx>
    Reviewed-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>

commit 0e99d51637dee0940a23556f3aee2e7c89bd016f
Author: Jeff Fan <jeff.fan@xxxxxxxxx>
Date:   Wed Nov 16 22:18:11 2016 +0800

    MdeModulePkg/CpuExceptionHanderLibNull: RegisterCpuInterruptHandler()
    
    Current CpuExceptionHanderLibNull instance returns EFI_SUCCESS for all three
    services. If platform does not want to hook the Exception vector for some
    modules (For example DxeCore), it could select this NULL instance in DSC 
file
    for those module. But some modules that want to consume
    RegisterCpuInterruptHandler() cannot use NULL instance. If platform does not
    select the correct library instance, it will does work. But the caller does 
not
    recognize it.
    
    This update is to return EFI_UNSUPPORTED on RegisterCpuInterruptHandler() in
    NULL instance instead of return EFI_SUCCESS. Once platform selects this NULL
    instance, the caller could know it from return status.
    
    Cc: Feng Tian <feng.tian@xxxxxxxxx>
    Cc: Michael D Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Jeff Fan <jeff.fan@xxxxxxxxx>
    Reviewed-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>

commit c773514d457265e9ada334572641e1b137c66aac
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Thu Nov 17 12:43:04 2016 -0800

    UefiCpuPkg/PiSmmCpuDxeSmm: Add volatile to mNumberToFinish
    
    Add volatile qualifier to mNumberToFinish to prevent GCC 5.4
    compiler from optimizing away required logic in ACPI S3 resume.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 672b80c8b74718e8c82373b9d59a06f5b10ddc8c
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Thu Nov 17 12:41:35 2016 -0800

    UefiCpuPkg/PiSmmCpuDxeSmm: TransferApToSafeState() use UINTN params
    
    Update TransferApToSafeState() use UINTN params to reduce the
    number of type casts required in these calls.  Also change
    the NumberToFinish parameter from UINT32* to UINTN
    NumberToFinishAddress to resolve issues with conversion from
    a volatile pointer to a non-volatile pointer.  The assembly
    code that receives the NumberToFinishAddress value must treat
    that memory location as a volatile to track the number of APs.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 0468303899bd1fa9a8a04e0dcf5de6e84beb0224
Author: Giri P Mudusuru <giri.p.mudusuru@xxxxxxxxx>
Date:   Sun Nov 13 23:06:26 2016 -0800

    IntelSiliconPkg: Add DxeSmbiosDataHobLib
    
    Added NULL Library constructor DxeSmbiosDataHobLib which adds SMBIOS
    records from gIntelSmbiosDataHobGuid HOB to SMBIOS table using
    SMBIOS protocol.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Giri P Mudusuru <giri.p.mudusuru@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit fa1beef5081ef3777b176c94bbf9a31b5f601b95
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Thu Nov 17 11:08:38 2016 -0800

    MdePkg/BaseSynchronizationLib: Fix function names in function headers
    
    Some of the function names in function header comment blocks in
    assembly files do not match the symbol name in the assembly sources.
    Update function header comment blocks to match symbol name.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 4cee954ea8063ab2a911e418d8a9e7a179df212b
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Wed Nov 16 14:37:15 2016 -0800

    MdePkg/BaseSynchronizationLib: Add volatile Interlocked*() APIs
    
    The SpinLock functions in the SynchronicationLib use volatile
    parameters to keep compiler from optimizing these functions
    too much.  The volatile keyword is missing from the Interlocked*()
    functions in this same library instance.  Update the library instance
    to consistently use volatile on all functions in the
    SynchronizationLib class.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 7375f3f11a70e3c7295ef7005f6723ced176ad0a
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Thu Nov 17 10:57:53 2016 -0800

    MdePkg/Include: Add volatile to SynchronizationLib parameters
    
    The SpinLock functions in the SynchronicationLib use volatile
    parameters to keep compiler from optimizing these functions
    too much.  The volatile keyword is missing from the Interlocked*()
    functions in this same library class.  Update the library class
    to consistently use volatile on all functions in this class.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Laszlo Ersek <lersek@xxxxxxxxxx>
    Cc: Andrew Fish <afish@xxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 8b66342c6bacc3270ca7a550ef703284eb4b95ce
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Wed Nov 16 16:01:57 2016 +0800

    SignedCapsulePkg Universal: Init local variables before using them
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit cf2ddcf13369af2aa98231dae5143e8bab06a00c
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Wed Nov 16 15:47:55 2016 +0800

    SignedCapsulePkg IniParsingLib: ASSERT to ensure 'Value' is not NULL
    
    Function GetStringFromDataFile() ensures its fourth (output) parameter
    will not be NULL when the return status is EFI_SUCCESS.
    
    This commit adds ASSERT as warnings for the case that will not happen.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>

commit b4dc05e854736c8f353a0f6e18ca85faa4d3785e
Author: Hao Wu <hao.a.wu@xxxxxxxxx>
Date:   Wed Nov 16 16:35:56 2016 +0800

    BaseTools/BuildEnv: Do not modify the env 'PACKAGES_PATH' in BuildEnv
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=236
    
    The script 'BuildEnv' modifies the value of the environment variable
    'PACKAGES_PATH' (line 44). The script will substitute the ':' symbol
    (separating multiple paths) with a space.
    
    This is not supposed to happen since users might later use 'PACKAGES_PATH'
    during the code-building process under a multiple-workspace scenario.
    
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Hao Wu <hao.a.wu@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>

commit 4e7872d2f71f511df155a9048f06761afce751da
Author: Maurice Ma <maurice.ma@xxxxxxxxx>
Date:   Wed Nov 16 19:22:32 2016 -0800

    CorebootPayloadPkg/CbSupportPei: Fix the memory map issue
    
    When coreboot reports memory range across 1MB, the current code
    cannot handle it properly. In this case the range should be
    adjusted to start from 1MB instead since the memory resource
    below 1MB has been preprocessed by CbSupportPei module.
    
    This patch fixed the coreboot + UEFI payload hang issue when
    running on QEMU due to incorrect memory map.
    
    Cc: Prince Agyeman <prince.agyeman@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Maurice Ma <maurice.ma@xxxxxxxxx>
    Reviewed-by: Prince Agyeman <prince.agyeman@xxxxxxxxx>

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

 


Rackspace

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