[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf baseline-only test] 67720: all pass
This run is configured for baseline tests only. flight 67720 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/67720/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 490acf8908f797982f367bfeb4bdf3ebe0764e42 baseline version: ovmf f8db6527da8678f1480f08ba99b745279e8d104a Last test of basis 67717 2016-09-15 10:49:16 Z 0 days Testing same since 67720 2016-09-15 17:19:47 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Ard Biesheuvel <ard.biesheuvel@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 490acf8908f797982f367bfeb4bdf3ebe0764e42 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Sep 15 14:23:11 2016 +0100 ArmVirtPkg/HighMemDxe: move to FDT client protocol Use the FDT client protocol rather than parsing the DT directly using fdtlib. While we're at it, update the code so it deals correctly with memory nodes that describe multiple disjoint regions in their "reg" properties, and make the code work with #address-cells/#size-cells properties of <1> as well as <2>. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> commit 969d2eb3875a700a223840d7ea415e78de4f8cbe Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Sep 15 13:33:23 2016 +0100 ArmVirtPkg/FdtClientDxe: add methods to iterate over memory nodes Add high level methods to iterate over all 'reg' properties of all DT nodes whose device_type properties have the value "memory". Since we are modifying the FdtClient protocol, update the protocol and the only existing implementation at the same time. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> commit cfc8d51c0cbf97b5e71cfd92dcc6c5760940214f Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Sep 15 14:15:14 2016 +0100 ArmVirtPkg/FdtClientDxe: report address and size cell count directly The FDT client protocol methods dealing with "reg" properties return the size of a "reg" element. Currently, we have hardcoded this as '8', since #address-cells == #size-cells == 2 in most cases. However, for different values, have a single 'reg' element size is not unambiguous, since - however unlikely - if #address-cells != #size-cells, we do not know which is which. So before adding more methods to the protocol, fix up this oversight. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> commit 38ed4a9e3a65185e7e7b3c891feab1ddc865fdb5 Author: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Date: Thu Sep 15 13:48:15 2016 +0100 ArmVirtPkg/FdtClientDxe: fix check for size of "reg" properties Currently, the code in FdtClientDxe assumes #address-cells/#size-cells values of <2>. Since DT "reg" properties always consist of <base, size> tuples, this means the size of the entire property should always be a multiple of 16 bytes (i.e, 4 * sizeof(UINT32), not 8. So fix this. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Ard Biesheuvel <ard.biesheuvel@xxxxxxxxxx> Reviewed-by: Laszlo Ersek <lersek@xxxxxxxxxx> _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |