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

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



This run is configured for baseline tests only.

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

Perfect :-)
All tests in this flight passed as required
version targeted for testing:
 ovmf                 a5991c8832c5301ec969c37cce5c1b332c7e0127
baseline version:
 ovmf                 653bde546200af46573cdfac88257f03b3420d88

Last test of basis    68037  2016-11-14 19:20:10 Z    0 days
Testing same since    68038  2016-11-14 23:47:04 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Giri P Mudusuru <giri.p.mudusuru@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 a5991c8832c5301ec969c37cce5c1b332c7e0127
Author: Giri P Mudusuru <giri.p.mudusuru@xxxxxxxxx>
Date:   Tue Nov 8 13:43:38 2016 -0800

    IntelSiliconPkg: Add PCD for Graphics VBT FFS GUID
    
    Added PCD PcdIntelGraphicsVbtFileGuid to store raw format
    Graphics Video BIOS Table (VBT) in FFS.
    
    Cc: Jiewen Yao <jiewen.yao@xxxxxxxxx>
    Cc: Star Zeng <star.zeng@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 fd0597aa9c26979789b272d1a05db98cbc970f8a
Author: Michael Kinney <michael.d.kinney@xxxxxxxxx>
Date:   Tue Nov 8 14:25:30 2016 -0800

    BaseTools/Scripts: Add BinToPcd utility
    
    https://bugzilla.tianocore.org/show_bug.cgi?id=228
    
    Add a utility that converts a binary file into a VOID* PCD value
    or a full DSC file VOID* PCD statement with support for all the
    DSC supported PCD sections.
    
    usage: BinToPcd [-h] [--version] -i INPUTFILE [-o OUTPUTFILE] [-p PCDNAME]
                    [-t {VPD,HII}] [-m MAXSIZE] [-f OFFSET] [-n VARIABLENAME]
                    [-g VARIABLEGUID] [-v] [-q] [--debug [0-9]]
    
    Convert a binary file to a VOID* PCD value or DSC file VOID* PCD statement.
    Copyright (c) 2016, Intel Corporation. All rights reserved.
    
    optional arguments:
      -h, --help        show this help message and exit
      --version         show program's version number and exit
      -i INPUTFILE, --input INPUTFILE
                        Input binary filename
      -o OUTPUTFILE, --output OUTPUTFILE
                        Output filename for PCD value or PCD statement
      -p PCDNAME, --pcd PCDNAME
                        Name of the PCD in the form
                        <PcdTokenSpaceGuidCName>.<PcdCName>
      -t {VPD,HII}, --type {VPD,HII}
                        PCD statement type (HII or VPD). Default is standard.
      -m MAXSIZE, --max-size MAXSIZE
                        Maximum size of the PCD. Ignored with --type HII.
      -f OFFSET, --offset OFFSET
                        VPD offset if --type is VPD. UEFI Variable offset if
                        --type is HII.
      -n VARIABLENAME, --variable-name VARIABLENAME
                        UEFI variable name. Only used with --type HII.
      -g VARIABLEGUID, --variable-guid VARIABLEGUID
                        UEFI variable GUID C name. Only used with --type HII.
      -v, --verbose     Increase output messages
      -q, --quiet       Reduce output messages
      --debug [0-9]     Set debug level
    
    This utility can be used in PCD value mode to convert a binary
    file into a string that can then be copied into the PCD value field
    of a VOID* PCD.  The following is an example of PCD value mode on
    an 8 byte test.bin file.
    
      BinToPcd.py -i test.bin
    
      {0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
    The DSC file VOID* PCD statement mode can be used to generate a
    complete PCD statement for the PCD section types that a DSC file
    supports:
    
      [PcdsFixedAtBuild]
      [PcdsPatchableInModule]
      [PcdsDynamicDefault]
      [PcdsDynamicExDefault]
      [PcdsDynamicVpd]
      [PcdsDynamicExVpd]
      [PcdsDynamicHii]
      [PcdsDynamicExHii]
    
    The PCD statement mode is useful when combined with a !include
    statement in a DSC file.  BinToPcd.py can be used to convert a
    binary file to a PCD statement in an output file, and that output
    file can be included into a DSC file in the matching PCD section
    to set the value of the PCD to the value from the binary file
    without having to copy the value into the DSC file.  Updates can be
    made to the included file without editing the DSC file.  Some
    example use cases are the setting the public key PCDs such as:
    
      gEfiSecurityPkgTokenSpaceGuid.PcdRsa2048Sha256PublicKeyBuffer
      gEfiSecurityPkgTokenSpaceGuid.PcdPkcs7CertBuffer
    
    The following example converts a public key binary file to a
    [PcdsFixedAtBuild] compatible PCD statement:
    
      BinToPcd.py -i PublicKey.bin -o PublicKey.pcd
        --pcd gEfiSecurityPkgTokenSpaceGuid.PcdPkcs7CertBufferkenSpaceGuid
    
    The PublicKey.pcd output file contains a single line:
    
      gEfiSecurityPkgTokenSpaceGuid.PcdPkcs7CertBuffer|{0x48, ...}
    
    A DSC file can be updated to include the PublicKey.pcd file:
    
      [PcdsFixedAtBuild]
      !include PublicKey.pcd
    
    Value examples
    ===============
      BinToPcd.py -i test.bin
        {0x68, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
    Normal examples:
    =================
      BinToPcd.py -i test.bin -p Guid.Token
        Guid.Token|{0x68, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
      BinToPcd.py -i test.bin -p Guid.Token -m 20
        Guid.Token|{0x68, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}|VOID*|20
    
    VPD examples:
    =============
      BinToPcd.py -i test.bin -p Guid.Token -t VPD
        Guid.Name|*|8|{0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
      BinToPcd.py -i test.bin -p Guid.Token -t VPD -f 20
        Guid.Name|20|8|{0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
      BinToPcd.py -i test.bin -p Guid.Token -t VPD -m 10
        Guid.Name|*|10|{0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
      BinToPcd.py -i test.bin -p Guid.Token -t VPD -f 20 -m 10
        Guid.Name|20|10|{0x48, 0x65, 0x6c, 0x6c, 0x6f, 0x20, 0x0d, 0x0a}
    
    HII examples:
    =============
      BinToPcd.py -i test.bin -p Guid.Token -t HII -g VarGuid -n VarName
        Guid.Name|L"VarName"|VarGuid|0|{0x48, 0x65, 0x6c, 0x6c}
    
      BinToPcd.py -i test.bin -p Guid.Token -t HII -g VarGuid -n VarName -f 8
        Guid.Name|L"VarName"|VarGuid|8|{0x48, 0x65, 0x6c, 0x6c}
    
    Cc: Yonghong Zhu <yonghong.zhu@xxxxxxxxx>
    Cc: Liming Gao <liming.gao@xxxxxxxxx>
    Contributed-under: TianoCore Contribution Agreement 1.0
    Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx>
    Reviewed-by: Liming Gao <liming.gao@xxxxxxxxx>
    Reviewed-by: Yonghong Zhu <yonghong.zhu@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®.