This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 7111e46fdebca0e03f6ddfcb029522c2fe68c74b
baseline version:
 ovmf                 2913ebb2b550f50a14f105e26995dd095e627ba4

Last test of basis    71953  2017-08-09 05:17:19 Z    0 days
Testing same since    71956  2017-08-09 16:20:20 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ruiyu Ni <ruiyu...@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 7111e46fdebca0e03f6ddfcb029522c2fe68c74b
Author: Ruiyu Ni <ruiyu...@intel.com>
Date:   Fri Aug 4 17:07:31 2017 +0800

    MdeModulePkg/NvmExpressDxe: Notify NVME HW when system reset happens
    
    Per NVM Express Spec, software should notify NVME HW when shutdown
    occurs.
    
    The NVME controller requires notification for shutdown as part of
    its management of internal structures. Even with FUA, failing to
    notify the NVME controller to shutdown power off causes the NVME
    controller to take quite some time to organize its tables on the
    next power on. This time exceeds the normal timeout, so we would
    fail to boot the NVME disk.
    
    The host should set the Shutdown Notification (CC.SHN) field to 01b
    to indicate a normal shutdown operation. The controller indicates
    when shutdown processing is completed by updating the Shutdown Status
    (CSTS.SHST) field to 10b.
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu...@intel.com>
    Reviewed-by: Hao A Wu <hao.a...@intel.com>

commit a607eb97ef92605d88ac72e551bae34da7c81394
Author: Ruiyu Ni <ruiyu...@intel.com>
Date:   Thu Jul 27 15:43:58 2017 +0800

    MdePkg/Nvme: Add NVME shutdown notification related macros
    
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Ruiyu Ni <ruiyu...@intel.com>
    Reviewed-by: Hao A Wu <hao.a...@intel.com>

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

Reply via email to