[ovmf baseline-only test] 74738: all pass

[ovmf baseline-only test] 74738: all pass

[Platform Team regression test user]

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 1e35fcc9ee8b6b991535d9d6731d0e04169b99c0
baseline version:
 ovmf                 7ebad830d6ab61f0395f6f4bae4156664bbd8086

Last test of basis    74733  2018-05-21 07:19:42 Z    2 days
Testing same since    74738  2018-05-23 13:49:23 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu.ni@intel.com>

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 1e35fcc9ee8b6b991535d9d6731d0e04169b99c0
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date:   Wed May 9 17:36:06 2018 +0800

    MdePkg/SmmPeriodicSmiLib: Get Periodic SMI Context More Robustly
    
    The PeriodicSmiDispatchFunction() in SmmPeriodicSmiLib may assert
    with "Bad CR signature".
    
    Currently, the SetActivePeriodicSmiLibraryHandler() function
    (invoked at the beginning of the PeriodicSmiDispatchFunction()
    function) attempts to locate the PERIODIC_SMI_LIBRARY_HANDLER_CONTEXT
    structure pointer for the current periodic SMI from a given
    EFI_SMM_PERIODIC_TIMER_REGISTER_CONTEXT (RegiserContext) structure
    pointer (using the CR macro).
    
    The RegisterContext structure pointer passed to the
    PeriodicSmiDispatchFunction() is assumed to point to the same
    RegisterContext structure address given to the
    SmmPeriodicTimerDispatch2 protocol Register() API in
    PeriodicSmiEnable().
    
    However, certain SmmPeriodicTimerDispatch2 implementation may copy
    the RegisterContext to a local buffer and pass that address as the
    context to PeriodicSmiDispatchFunction() in which case usage of the
    CR macro to find the parent structure base fails.
    
    The patch uses the LookupPeriodicSmiLibraryHandler() function to
    find the PERIODIC_SMI_LIBRARY_HANDLER_CONTEXT structure pointer.
    This works even in this scenario since the DispatchHandle returned
    from the SmmPeriodicTimerDispatch2 Register() function uniquely
    identifies that registration.
    
    Contributed-under: TianoCore Contribution Agreement 1.1
    Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
    Cc: Michael D Kinney <michael.d.kinney@intel.com>
    Reviewed-by: Liming Gao <liming.gao@intel.com>

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