* [ovmf baseline-only test] 67848: all pass
@ 2016-10-08 9:13 Platform Team regression test user
0 siblings, 0 replies; only message in thread
From: Platform Team regression test user @ 2016-10-08 9:13 UTC (permalink / raw)
To: xen-devel, osstest-admin
This run is configured for baseline tests only.
flight 67848 ovmf real [real]
http://osstest.xs.citrite.net/~osstest/testlogs/logs/67848/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf f6c8e67db9233562fd3ddc6bf7d23f0bb5fb115b
baseline version:
ovmf f9c3b1b5343f53705f1ab72c55c1db440b01f36f
Last test of basis 67846 2016-10-07 22:50:43 Z 0 days
Testing same since 67848 2016-10-08 04:50:27 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Michael Kinney <michael.d.kinney@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 f6c8e67db9233562fd3ddc6bf7d23f0bb5fb115b
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Mon Oct 3 11:16:46 2016 -0700
QuarkPlatformPkg/RecoveryOemHookLib: Remove RecoveryOemHookLib
Remove the RecoveryOemHookLib class and instance that is no
longer used by any modules.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 963236092b48013e34c5c889ae4c90b34bd8aef5
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Mon Oct 3 11:16:19 2016 -0700
QuarkPlatformPkg: Add ForceRecovery UEFI application
https://bugzilla.tianocore.org/show_bug.cgi?id=138
Add the ForceRecovery UEFI application to the Quark.dsc file
so this application can be put onto an SD card or USB drive
to test the Galileo firmware recovery feature.
The library mappings to the RecoveryOemHookLib are also
removed becuse this library is not longer used by any modules.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 8ac6966704fe2d7bfa62a826da3927f860e0b241
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Mon Oct 3 11:15:02 2016 -0700
QuarkPlatformPkg/PlatformHelperLib: Remove PlatformDebugPortGetChar8()
Remove the library function PlatformDebugPortGetChar8() from the
PlatformHelperLib that is no longer used by any modules.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 69a0854b8fa8317dcf459c6e753fefa3a89340e6
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Mon Oct 3 11:13:42 2016 -0700
QuarkPlatformPkg/PlatformInit: Fix recovery detection issues
https://bugzilla.tianocore.org/show_bug.cgi?id=137
https://bugzilla.tianocore.org/show_bug.cgi?id=139
There are four supported methods to generate a boot mode of
BOOT_IN_RECOVERY_MODE on the Galileo platforms:
* Detect a corrupt FV
* Detect a forced recovery from the ForceRecovery UEFI application
that sets a bit in a sticky R/W register
* The RESET button for the Arduino shield is held while the system
is powered up
* The RESET button for the Arduino shield is held while the system
is rebooted using the REBOOT button.
The logic in the PlatformInit module is cleaned up and updated to
support all three of the recovery detection methods. The clean
ups include:
* Remove extra debug messages
* Remove user input from serial port
In addition, once one of the recovery methods is detected and a
boot mode of BOOT_IN_RECOVERY_MODE is set, the Galileo platforms
would get an error attempting to use the USB host controller to
detect and read a recovery image from a USB drive. The issue is
the IMR protection registers are programmed to prevent DMA to
memory owned by the PEI Core. The IMR register programming is
updated to allow DMA to memory that is allocated by the recovery
modules using the PEI AllocatePages() service.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 9c3dea8ddab0272729d106ab0fda632fd63ec2ec
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Mon Oct 3 11:09:58 2016 -0700
QuarkPlatformPkg/ForceRecovery: Add UEFI application to force recovery
https://bugzilla.tianocore.org/show_bug.cgi?id=138
This UEFI Application sets a sticky bit that persists across reset
to force a boot mode of BOOT_IN_RECOVERY_MODE. It then performs
a warm reset using the UEFI Runtime Service ResetSystem().
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 5f82e02a4b40f25462f0d592e85071bdeb80a2bd
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Tue Oct 4 10:55:24 2016 -0700
QuarkSocPkg/QncSmmDispatcher: Fix use after free issue
Update Quark North Cluster SMM dispatcher logic to handle
case where an SMI handler unregisters itself.
https://bugzilla.tianocore.org/show_bug.cgi?id=51
This issue was reproduced using the unit test at:
https://github.com/mdkinney/edk2/tree/Bug51/Reproduce
An ASSERT() is generated the 4th time the periodic SMI
handler is triggered when the periodic SMI handler
unregisters itself. After applying this patch, the
DEBUG() message from the periodic SMI handler in this
unit test is generated 4 times, the periodic SMI handler
is unregistered, and the UEFI Shell works as expected.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
commit 29f169d17a0f09cd1e05c984da5965e08f2b696e
Author: Michael Kinney <michael.d.kinney@intel.com>
Date: Tue Oct 4 20:03:24 2016 -0700
QuarkSocPkg/QncSmmDispatcher: Fix context passed to SMI handlers
https://bugzilla.tianocore.org/show_bug.cgi?id=136
1) Add CallbackContext field to the DATABASE_RECORD structure that
is set to the RegisterContent value passed to QNCSmmCoreRegister().
This is the content that must be passed to the SMI handler when
its source is triggered.
2) Update usage of ChildContext field in the DATABASE_RECOD to use
CopyMem() instead of structure assignments to avoid compiler
use of memcpy() intrinsics
This issue was reproduced using the unit test at:
https://github.com/mdkinney/edk2/tree/Bug51/Reproduce
An ASSERT() is generated the first time the periodic SMI
handler is triggered. After applying this patch, the
DEBUG() messages from the periodic SMI handler in this
unit test are generated.
Cc: Kelly Steele <kelly.steele@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Michael Kinney <michael.d.kinney@intel.com>
Reviewed-by: Kelly Steele <kelly.steele@intel.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-10-08 9:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-10-08 9:13 [ovmf baseline-only test] 67848: all pass Platform Team regression test user
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).