[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [ovmf baseline-only test] 38216: all pass
This run is configured for baseline tests only. flight 38216 ovmf real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38216/ Perfect :-) All tests in this flight passed version targeted for testing: ovmf f40577c3563fcad7fc512617925d0574a7c64e2f baseline version: ovmf 5d3a9896f0cbb0c8c3d375d9f82a7e397be862a7 Last test of basis 38214 2015-10-27 03:50:14 Z 1 days Testing same since 38216 2015-10-28 06:20:55 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Jaben Carsey <jaben.carsey@xxxxxxxxx> Jin Eric <eric.jin@xxxxxxxxx> Laszlo Ersek <lersek@xxxxxxxxxx> Liming Gao <liming.gao@xxxxxxxxx> Michael Kinney <michael.d.kinney@xxxxxxxxx> Qiu Shumin <shumin.qiu@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 f40577c3563fcad7fc512617925d0574a7c64e2f Author: Michael Kinney <michael.d.kinney@xxxxxxxxx> Date: Mon Oct 26 16:40:52 2015 +0000 UefiCpuPkg: PiSmmCpuDxeSmm: Remove unused references to SmmLib The PiSmmCpuDxeSmm module does not use any services from the SmmLib. This change removes the SmmLib from PiSmmCpuDxeSmm module and also removes the lib mapping in the UefiCpuPkg DSC file because no other modules in the UefiCpuPkg use the SmmLib. Removal of SmmLib is now possible because the only API call to it, ClearSmi(), was ultimately removed from PiSmmCpuDxeSmm -- see the "BUGBUG" comment in git commit 529a5a86. Cc: "Yao, Jiewen" <jiewen.yao@xxxxxxxxx> Cc: Jeff Fan <jeff.fan@xxxxxxxxx> Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Michael Kinney <michael.d.kinney@xxxxxxxxx> Reviewed-by: "Yao, Jiewen" <jiewen.yao@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18673 6f19259b-4bc3-4df7-8a09-765794883524 commit 0f2eb31c764685a1919b52f414bea44ea37580a2 Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:46 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: clean up includes and libraries Before introducing the SMM driver interface, clean up #include directives and [LibraryClasses] by: - removing what's not directly used (HobLib and UefiLib), - adding what's used but not spelled out (DevicePathLib), - sorting the result. This helps with seeing each source file's dependencies and with determining the library classes for the SMM driver. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18672 6f19259b-4bc3-4df7-8a09-765794883524 commit 1767877a31b3ce191ddae6cb9aefba99a733fe20 Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:39 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: split out runtime DXE specifics In preparation for introducing an SMM interface to this driver, move the following traits to separate files, so that we can replace them in the new SMM INF file: - Protocol installations. The SMM driver will install protocol interfaces in the SMM protocol database, using SMM services. - Virtual address change handler and pointer conversions. SMM drivers run with physical mappings and pointers must not be converted. There are further restrictions and changes for an SMM driver, but the rest of the code either complies with those already, or will handle the changes transparently. For example: - SMM drivers have access to both UEFI and SMM protocols in their entry points (see the PI spec 1.4, "1.7 SMM Driver Initialization"), - MemoryAllocationLib has an SMM instance that serves allocation requests with the gSmst->SmmAllocatePool() service transparently, allocating runtime-marked SMRAM. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18671 6f19259b-4bc3-4df7-8a09-765794883524 commit 109301e5a14ec4bfd0ce93e15439e30d7ccd8b0a Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:33 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: no dual addressing needed Currently the EFI_FW_VOL_INSTANCE and ESAL_FWB_GLOBAL structures declare the following entries as arrays, with two entries each: - EFI_FW_VOL_INSTANCE.FvBase[2] - ESAL_FWB_GLOBAL.FvInstance[2] In every case, the entry at subscript zero is meant as "physical address", while the entry at subscript one is meant as "virtual address" -- a pointer to the same object. The virtual address entry is originally initialized to the physical address, and then it is converted to the virtual mapping in FvbVirtualddressChangeEvent(). Functions that (a) read the listed fields and (b) run both before and after the virtual address change event -- since this is a runtime DXE driver -- derive the correct array subscript by calling the EfiGoneVirtual() function from UefiRuntimeLib. The problem with the above infrastructure is that it's entirely superfluous. EfiGoneVirtual() "knows" whether EFI has gone virtual only because the UefiRuntimeLib constructor registers the exact same kind of virtual address change callback, and the callback flips a static variabe to TRUE, and EfiGoneVirtual() queries that static variable. In effect this means for QemuFlashFvbServicesRuntimeDxe: "when there is a virtual address change, convert the entries with subscript one from physical to virtual, and from then on use the entries with subscript one". This would only make sense if QemuFlashFvbServicesRuntimeDxe ever needed the original (physical) addresses (ie. the entries with subscript zero) after the virtual address change, but that is not the case. Replace the arrays with single elements. The subscript zero elements simply disappear, and the single elements take the role of the prior subscript one elements. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18670 6f19259b-4bc3-4df7-8a09-765794883524 commit f97a5b5e4cab1f01f92a0899cc95b92c5a9f3ed3 Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:26 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: remove FvbScratchSpace field The ESAL_FWB_GLOBAL.FvbScratchSpace array is never initialized (it contains garbage from AllocateRuntimePool()). Its element at subscript one (=FVB_VIRTUAL), containing garbage as well, is converted to virtual mapping. Then the array is never used again. Remove it. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18669 6f19259b-4bc3-4df7-8a09-765794883524 commit a05aff56554f4ff74629d13db92260d504f8cb5b Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:20 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: remove FvbDevLock field The EFI_FW_VOL_INSTANCE.FvbDevLock member is initialized and then never used. Remove it. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18668 6f19259b-4bc3-4df7-8a09-765794883524 commit 2ff2a0e1a85103aa8584e8451f9e3e48020960bf Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:14 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: fix VALID_ARCHITECTURES in INF We build this driver for X64 as well -- the comment isn't overly important, but it shouldn't be misleading. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18667 6f19259b-4bc3-4df7-8a09-765794883524 commit ea0d111efe756dcc53d355bc25d17d9a925c6007 Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:08 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: rewrap source code to 79 chars Some of the line lengths in this driver are atrocious. While we have to put up with the status quo outside of OvmfPkg, we can at least rewrap this driver before refactoring it. In the FvbInitialize() function there's no way around introducing two local variables, just for the sake of sensibly rewrapping the code. Furthermore, in "FwBlockService.c" the function comment blocks are now indented; their original position causes diff to print bogus function names at the top of hunks. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18666 6f19259b-4bc3-4df7-8a09-765794883524 commit 141f0c644512e4da3bad7a0382fe82aa8c460762 Author: Laszlo Ersek <lersek@xxxxxxxxxx> Date: Mon Oct 26 14:58:01 2015 +0000 OvmfPkg: QemuFlashFvbServicesRuntimeDxe: strip trailing whitespace Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx> Reviewed-by: Jordan Justen <jordan.l.justen@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18665 6f19259b-4bc3-4df7-8a09-765794883524 commit 490ce43d92132653a6664971218e1cb330556391 Author: Qiu Shumin <shumin.qiu@xxxxxxxxx> Date: Mon Oct 26 13:28:01 2015 +0000 ShellPkg: Fix 'EfiShellExecute' doesn't get command status correctly. 1. Add a new function 'RunShellCommand' to return command status, thus 'EfiShellExecute' can get the command return status of 'CommandLine'. 2. Refine the code logic of 'EfiShellExecute' to make the new image of shell be loaded only if 'Environment' isn't NULL. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Qiu Shumin <shumin.qiu@xxxxxxxxx> Signed-off-by: Jin Eric <eric.jin@xxxxxxxxx> Signed-off-by: Jaben Carsey <jaben.carsey@xxxxxxxxx> Reviewed-by: Ruiyu Ni <ruiyu.ni@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18664 6f19259b-4bc3-4df7-8a09-765794883524 commit c2305a4af8c78b5ce553e133e86140817851a9e8 Author: Liming Gao <liming.gao@xxxxxxxxx> Date: Mon Oct 26 08:48:39 2015 +0000 BaseTools: Add MultipleWorkspace.py in the common dependency. Add new added MultipleWorkspace.py in the common dependency to freeze python tools for Windows. Contributed-under: TianoCore Contribution Agreement 1.0 Signed-off-by: Liming Gao <liming.gao@xxxxxxxxx> Reviewed-by: Yonghong Zhu <yonghong.zhu@xxxxxxxxx> git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@18663 6f19259b-4bc3-4df7-8a09-765794883524 _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |