Linux UEFI Validation Project v1.2-rc2 release
by Neri, Ricardo
Hi,
On behalf of Matt Fleming, I am releasing the second candidate for v1.2.
You can pull it from here:
https://download.01.org/linux-uefi-validation/v1.2/luv-live-v1.2-rc2.tar.bz2
Starting with this release I've also signed a sha256 checksum of the
live image,
The signed sha256 checksum can be retrieved from here:
https://download.01.org/linux-uefi-validation/v1.2/sha256sums.asc
Please note that this contains the signed sha256 checksums for the two
release candidates of v1.2.
Changes in this release...
1. Timestamp information for selected test suites
Normally, you run LUV and you go to grab a cup of coffee. Thus, you
might be missing important information about how long it takes to run a
particular test. Gayatri Kammela implemented time logging functionality.
This is implemented at the unit test granularity. This adds another
dimension to the validation as there might be tests that take
unexpectedly too long to complete. As of v1.2-rc2, this feature is
available for CHIPSEC, FWTS and EFIVARFS.
2. A new test results parsing schema
Now that time logging functionality is available, LUV parsers need to
process more information. In order to support timestamps, a new parsing
schema, 1.1 is available:
schema_version time test_suite unit_test RESULT #passes #fails #aborts
#skips
On 1.1, the timestamp is the second field of the parsed results.
For the test suites that do not support time logging yet, the 1.0
parsing schema is still supported.
Also, while working on the new schema, Matt found that the testing
information from FWTS was not being parsed correctly. Thus, he fixed the
issue and in this release you might find more useful data from FWTS!
3. CHIPSEC is available on LUV!
After being disabled for several months, We went ahead and enabled the
CHIPSEC: Platform Security Assessment Framework
(https://github.com/chipsec/chipsec) again. CHIPSEC is known to fail on
ASUS P8H67-M LE (see issue #7
https://github.com/01org/luv-yocto/issues/7 ). We ran the test suite on
a number of different systems and it worked well. If it fails for you,
please contact us or comment on the aforementioned issue. We will
greatly appreciate your inputs.
The shortlog looks like this,
Gayatri Kammela (4):
luv: Add timestamp to luv-parser-fwts
luv: Add timestamp to luv-parser-efivarfs
luv: Add timestamp to luv-parser-chipsec
CHIPSEC: Enable the CHIPSEC test suite
Matt Fleming (2):
luv-test-parser: Add timestamp field to schema
fwts: Fix luv-parser-fwts INFO results
Thanks and BR,
Ricardo Neri, Intel Open Source Technology Center
7 years, 8 months
[PATCH] CHIPSEC: Enable the CHIPSEC test suite
by Gayatri Kammela
The CHIPSEC test suite was disabled in the commit #af66ed38bad4
because of hang/freeze issues when running it
ASUS P8H67-M LE hardware as described in issue #7.
Enabling and testing by running only ”Chipsec” on
various platforms like Haswell,Broad well,HP Elite Book 8470p,
Rainbow pass gives fair results and avoids misinterpretations
like Haswell takes long time to run and it might be convincing
that it is due to CHIPSEC but it is because of FWTS.
All the above platforms give no issues with enabling the Chipsec.
If there are other platforms that reports the same problem
like in the issue#7 we would have had more data to investigate
and debug further.
But users are starting to ask for this test suite to be included
in the luv-live-image.There's no sense in disabling it entirely
if the hangs described in issue #7 are only triggered on a
few specific platforms.So let's enable CHIPSEC for users test out!
Cc: Matt Fleming <matt.fleming(a)intel.com>
signed-off-by: Gayatri Kammela <gayatri.kammela(a)intel.com>
---
meta-luv/recipes-core/images/core-image-efi-initramfs.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta-luv/recipes-core/images/core-image-efi-initramfs.bb b/meta-luv/recipes-core/images/core-image-efi-initramfs.bb
index a1e2aa14fdf2..1dd53e6f3278 100644
--- a/meta-luv/recipes-core/images/core-image-efi-initramfs.bb
+++ b/meta-luv/recipes-core/images/core-image-efi-initramfs.bb
@@ -7,7 +7,7 @@ IMAGE_INSTALL = "\
kernel-image fwts bash coreutils gawk grep util-linux-agetty \
util-linux-mount util-linux-umount kmod sed tar net-tools \
shadow util-linux procps efivarfs-test \
- psplash kexec vmcore-dmesg kernel-efi-warnings bits \
+ psplash chipsec kexec vmcore-dmesg kernel-efi-warnings bits \
"
export IMAGE_BASENAME = "core-image-efi-initramfs"
--
1.9.1
7 years, 8 months
[GIT PULL]: Add new timestamp field to luv results
by Matt Fleming
From: Matt Fleming <matt.fleming(a)intel.com>
https://github.com/01org/luv-yocto/pull/45
For the purposes of both debugging and optimizing it's really helpful to
have a timestamp field included in the test results log so that we can
see how long each unit test is taking to execute.
These changes should provide a start for debugging #26
Gayatri Kammela (2):
luv: Add timestamp to luv-parser-fwts
luv: Add timestamp to luv-parser-efivarfs
Matt Fleming (2):
luv-test-parser: Add timestamp field to schema
fwts: Fix luv-parser-fwts INFO results
.../efivarfs/efivarfs-test/luv-parser-efivarfs | 12 ++++--
meta-luv/recipes-core/fwts/fwts/luv-parser-fwts | 8 ++--
.../initscripts/initscripts/luv-test-parser | 46 +++++++++++++++-------
3 files changed, 46 insertions(+), 20 deletions(-)
--
1.9.3
7 years, 8 months
[PATCH] luv: Add timestamp to luv-parser-chipsec
by Gayatri Kammela
Modify luv-parser-chipsec to get a timestamp on
frontline of each unittest when chipsec is executed
Changes will meet the schema 1.1 version updated
in the luv-test-parser file by Matt Fleming and now the
format looks like this
"1.1 timestamp chipsec unittest RESULT 1 0 0 0"
Since the CHIPSEC test suite is enabled,it is good to add
the timestamp to CHIPSEC as well.Patch provides the clear
understanding of how much time did each of the unittests take to run
Cc: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
Cc: Matt Fleming <matt.fleming(a)intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela(a)intel.com>
---
.../recipes-core/chipsec/chipsec/luv-parser-chipsec | 20 ++++++++++++++++----
1 files changed, 16 insertions(+), 4 deletions(-)
diff --git a/meta-luv/recipes-core/chipsec/chipsec/luv-parser-chipsec b/meta-luv/recipes-core/chipsec/chipsec/luv-parser-chipsec
index a91067abb171..c53a8759bd49 100644
--- a/meta-luv/recipes-core/chipsec/chipsec/luv-parser-chipsec
+++ b/meta-luv/recipes-core/chipsec/chipsec/luv-parser-chipsec
@@ -8,25 +8,37 @@ awk ' /\[\+\] imported/ {
}
/\[\*\] SKIPPED/ {
+ "date +%H:%M:%S:%N" | getline current_time;
+ close ("date +%H:%M:%S:%N")
if (test_strs[$3]) {
- printf("1.0 chipsec %s RESULT 0 0 0 0 1\n", $3);
+ printf("1.1 %s chipsec %s RESULT 0 0 0 0 1\r\n", current_time, $3);
+ fflush("");
}
}
/^ERROR/ {
+ "date +%H:%M:%S:%N" | getline current_time;
+ close ("date +%H:%M:%S:%N")
if (test_strs[$2]) {
- printf("1.0 chipsec %s RESULT 0 0 0 1 0\n", $2);
+ printf("1.1 %s chipsec %s RESULT 0 0 0 1 0\r\n", current_time, $2);
+ fflush("");
}
}
/\[\-\] FAILED/ {
+ "date +%H:%M:%S:%N" | getline current_time;
+ close ("date +%H:%M:%S:%N")
if (test_strs[$3]) {
- printf("1.0 chipsec %s RESULT 0 1 0 0 0\n", $3);
+ printf("1.1 %s chipsec %s RESULT 0 1 0 0 0\r\n", current_time, $3);
+ fflush("");
}
}
/\[\+\] PASSED/ {
+ "date +%H:%M:%S:%N" | getline current_time;
+ close ("date +%H:%M:%S:%N")
if (test_strs[$3]) {
- printf("1.0 chipsec %s RESULT 1 0 0 0 0\n", $3);
+ printf("1.1 %s chipsec %s RESULT 1 0 0 0 0\r\n", current_time, $3);
+ fflush("");
}
}'
--
1.9.1
7 years, 8 months
[GIT PULL] Mark boot partition as EFI System Partition (ESP)
by Matt Fleming
From: Matt Fleming <matt.fleming(a)intel.com>
https://github.com/01org/luv-yocto/pull/44
We've had reports of some Dell firmware not being able to boot the live
images automatically, which is probably caused by marking the bootable
partition as fat (0xc) and not EFI System Partition (0xef)
Matt Fleming (1):
luv-live-image: Mark boot partition as EFI System Partition (ESP)
meta-luv/recipes-core/images/luv-live-image.bb | 11 +++++++++++
1 file changed, 11 insertions(+)
--
1.9.3
7 years, 8 months
[PATCH] luv-test-manager : Append timestamp to the luv-results file name
by Gayatri Kammela
To address the issue #22 on https://github.com/01org/luv-yocto/issues
Modify luv-test-manager to append the timestamp to luv-results file name
so as to store the results from multiple boots on the same USB stick
The luv-results parition will contain results with file names
luv-results.2014-11-25_12-39-08 after one or multiple boots and also
print the same information inside luv.results file
Cc: Ricardo Neri <ricardo.neri-calderon(a)linux.intel.com>
Cc: Matt Fleming <matt.fleming(a)intel.com>
Signed-off-by: Gayatri Kammela <gayatri.kammela(a)intel.com>
---
meta-luv/recipes-core/initscripts/initscripts/luv-test-manager | 9 ++++++---
1 file changed, 6 insertions(+), 3 deletions(-)
diff --git a/meta-luv/recipes-core/initscripts/initscripts/luv-test-manager b/meta-luv/recipes-core/initscripts/initscripts/luv-test-manager
index 0ffa20aa5199..2b1053c9ba26 100644
--- a/meta-luv/recipes-core/initscripts/initscripts/luv-test-manager
+++ b/meta-luv/recipes-core/initscripts/initscripts/luv-test-manager
@@ -18,8 +18,8 @@ psplash_write() {
# correct partition, mount using the disk's UUID. If the partition
# cannot be mounted, test results are not saved.
-LUV_SAVE_RAW_DIR=/dev/null
-LUV_SAVE_PARSED_DIR=/dev/null
+#LUV_SAVE_RAW_DIR=/dev/null
+#LUV_SAVE_PARSED_DIR=/dev/null
LUV_SAVE_RESULTS_DIR=/dev/null
LUV_STORAGE=/mnt/luv-storage/
@@ -30,7 +30,8 @@ mkdir -p ${LUV_STORAGE}
if [ $? -eq 0 ]; then
mount ${LUV_DISK_DEVICE} ${LUV_STORAGE}
if [ $? -eq 0 ]; then
- LUV_SAVE_RESULTS_DIR=${LUV_STORAGE}luv-results/
+ tstamp=$(date +"%Y-%m-%d_%H-%M-%S")
+ LUV_SAVE_RESULTS_DIR=${LUV_STORAGE}luv.$tstamp-results/
mkdir -p ${LUV_SAVE_RESULTS_DIR}raw/
[ $? -eq 0 ] && LUV_SAVE_RAW_DIR=${LUV_SAVE_RESULTS_DIR}raw/
@@ -88,6 +89,8 @@ psplash_write "PROGRESS 0"
cat <<EOF | tee ${LUV_SAVE_RESULTS_DIR}/luv.results > /tmp/luv.results
$luv_version
+Date and time of the system :`date +"%a %b %d %Y_%H-%M-%S"\ `
+
Test results summary:
EOF
--
1.9.1
7 years, 8 months
[GIT PULL] First attempt at a simple wrapper for configuring luv-yocto
by Matt Fleming
From: Matt Fleming <matt.fleming(a)intel.com>
https://github.com/01org/luv-yocto/pull/43
issue #31 explains the reasons it'd be good to have some simple to use
script to configure the build environment. Basically, having manual
steps makes it far too easy to get one of them wrong or skip it
accidentally.
This is a first attempt at providing a simple to use single wrapper.
Matt Fleming (2):
luv: Add custom {bblayers,local}.conf
luv-setup: Tiny wrapper to make configuration easier
luv-setup | 9 ++
meta-luv/conf/bblayers.conf.sample | 17 +++
meta-luv/conf/local.conf.sample | 235 +++++++++++++++++++++++++++++++++++++
3 files changed, 261 insertions(+)
create mode 100755 luv-setup
create mode 100644 meta-luv/conf/bblayers.conf.sample
create mode 100644 meta-luv/conf/local.conf.sample
--
1.9.3
7 years, 8 months
