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

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

This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed
version targeted for testing:
 ovmf                 bd3afeb1d62c68d8144d39e82bb188b2af3ca60c
baseline version:
 ovmf                 a2e619821a791de5cd65cd2c757de0a8aa7f138c

Last test of basis    38279  2015-11-15 23:50:22 Z    2 days
Testing same since    38304  2015-11-18 03:06:22 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@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 bd3afeb1d62c68d8144d39e82bb188b2af3ca60c
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Mon Nov 16 18:29:14 2015 +0000

    MdeModulePkg: SmmLockBoxPeiLib: work without EFI_PEI_SMM_COMMUNICATION_PPI
    
    The RestoreLockBox() and RestoreAllLockBoxInPlace() functions handle the
    case when EFI_PEI_SMM_COMMUNICATION_PPI.Communicate() returns
    EFI_NOT_STARTED: they access the SMRAM directly, for restoring LockBox
    data.
    
    This occurs if a PEIM needs to restore LockBox data *before* the SMBASE is
    relocated and the SMI handler is installed for all processors.
    
    One such PEIM is UefiCpuPkg/Universal/Acpi/S3Resume2Pei. On the S3 resume
    path, in function S3RestoreConfig2(), LockBox data are restored *before*
    the SmmRestoreCpu() function of UefiCpuPkg/PiSmmCpuDxeSmm is called via
    SmmS3ResumeState->SmmS3ResumeEntryPoint. (The latter SmmRestoreCpu()
    function is responsible for the SMBASE relocation.)
    
    If a platform knows that its PEIMs restore LockBox data *only* before
    SMBASE relocation -- e.g., due to S3Resume2Pei being the platform's only
    SmmLockBoxPeiLib client --, then the platform might not want to include
    "UefiCpuPkg/PiSmmCommunication/PiSmmCommunicationPei.inf" at all (hence
    not provide EFI_PEI_SMM_COMMUNICATION_PPI) -- because all of those
    restores would be serviced by direct SMRAM access anyway.
    
    Currently the absence of EFI_PEI_SMM_COMMUNICATION_PPI is not supported by
    SmmLockBoxPeiLib, but it's not hard to implement. Handle it the same as
    when EFI_PEI_SMM_COMMUNICATION_PPI.Communicate() returns EFI_NOT_STARTED:
    restore LockBox data directly from SMRAM.
    
    Suggested-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    
    git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18823 
6f19259b-4bc3-4df7-8a09-765794883524

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