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

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



This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 bb767506b265b1cdbf0dbec58c9a3f4c6be6ab2b
baseline version:
 ovmf                 4e3b05a49f454bc257252ae9090421e3c8447737

Last test of basis    68114  2016-11-28 14:19:32 Z    0 days
Testing same since    68116  2016-11-28 20:21:13 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Laszlo Ersek <lersek@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 bb767506b265b1cdbf0dbec58c9a3f4c6be6ab2b
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Thu Nov 24 20:49:43 2016 +0100

    UefiCpuPkg/PiSmmCpuDxeSmm: handle dynamic PcdCpuMaxLogicalProcessorNumber
    
    "UefiCpuPkg/UefiCpuPkg.dec" already allows platforms to make
    PcdCpuMaxLogicalProcessorNumber dynamic, however PiSmmCpuDxeSmm does not
    take this into account everywhere. As soon as a platform turns the PCD
    into a dynamic one, at least S3 fails. When the PCD is dynamic, all
    PcdGet() calls translate into PCD DXE protocol calls, which are only
    permitted at boot time, not at runtime or during S3 resume.
    
    We already have a variable called mMaxNumberOfCpus; it is initialized in
    the entry point function like this:
    
    > //
    > // If support CPU hot plug, we need to allocate resources for possibly
    > // hot-added processors
    > //
    > if (FeaturePcdGet (PcdCpuHotPlugSupport)) {
    >   mMaxNumberOfCpus = PcdGet32 (PcdCpuMaxLogicalProcessorNumber);
    > } else {
    >   mMaxNumberOfCpus = mNumberOfCpus;
    > }
    
    There's another use of the PCD a bit higher up, also in the entry point
    function:
    
    > //
    > // Use MP Services Protocol to retrieve the number of processors and
    > // number of enabled processors
    > //
    > Status = MpServices->GetNumberOfProcessors (MpServices, &mNumberOfCpus,
    >                        &NumberOfEnabledProcessors);
    > ASSERT_EFI_ERROR (Status);
    > ASSERT (mNumberOfCpus <= PcdGet32 (PcdCpuMaxLogicalProcessorNumber));
    
    Preserve these calls in the entry point function, and replace all other
    uses of PcdCpuMaxLogicalProcessorNumber -- there are only reads -- with
    mMaxNumberOfCpus.
    
    For PcdCpuHotPlugSupport==TRUE, this is an unobservable change.
    
    For PcdCpuHotPlugSupport==FALSE, we even save SMRAM, because we no longer
    allocate resources needlessly for CPUs that can never appear in the
    system.
    
    PcdCpuMaxLogicalProcessorNumber is also retrieved in
    "UefiCpuPkg/Library/SmmCpuFeaturesLib/SmmCpuFeaturesLib.c",  but only in
    the library instance constructor, which runs even before the entry point
    function is called.
    
    Cc: Igor Mammedov <imammedo@xxxxxxxxxx>
    Cc: Jeff Fan <jeff.fan@xxxxxxxxx>
    Cc: Jordan Justen <jordan.l.justen@xxxxxxxxx>
    Cc: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Bugzilla: https://bugzilla.tianocore.org/show_bug.cgi?id=116
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Jeff Fan <jeff.fan@xxxxxxxxx>

commit 520150302c6ee3a4809f00c25dc3b597334d96ef
Author: Star Zeng <star.zeng@xxxxxxxxx>
Date:   Fri Nov 25 10:38:02 2016 +0800

    SecurityPkg Tcg2ConfigDxe: Align Attempt TPM Device help with options
    
    Current options only have TPM 1.2 and TPM 2.0,
    but help shows Disable, TPM1.2, or TPM2.0,
    they are mismatched.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Chao Zhang <chao.b.zhang@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Star Zeng <star.zeng@xxxxxxxxx>
    Reviewed-by: Jiewen Yao <jiewen.yao@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®.