June 2014 - Luv - Ml01.01.Org

by Anbazhagan, Baraneedharan

Hi, Once the test completed, it indicates passed test count and failed count and couldn't get the log to investigate which one failed. Could you please provide instruction on how to get the complete log? Thanks. -Baranee CONFIDENTIALITY NOTICE: The information contained in this e-mail and any accompanying documents may contain information which is HP confidential or otherwise protected from disclosure. This transmission may also be protected by the attorney-client privilege, the attorney work-product privilege, or both. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.

7 years, 7 months

2
4
0 / 0

luv v1.0-rc2 release

by Matt Fleming

It's been 4 weeks since -rc1 so it's time for another release candiate. Note that the live image is not yet available for download, but should hopefully be up in the usual place by the end of the day - https://01.org/linux-uefi-validation/downloads. Here are some stats for this release candidate, 1. luv-live-v1.0-rc2.img has a 8388608b (34%) increase in size which comes from commit 63a4f05 ("luv-live-image: Create second partition for test results"). This takes the live image to about 32MB. Of course this compresses nicely and difference between the .bz2 files for -rc1 and -rc2 is only 17613 bytes, with both .bz2 images being roughly 22MB in size. 2. 14 new commits (1 new test suite) Most of the work this release cycle has gone into storing the test results onto the live media which was essential in allowing us to close the following issue https://github.com/01org/luv-yocto/issues/2. Also, new recipes were added for more bootloaders (gummiboot and efilinux) as well as CHIPSEC, expanding our test coverage. A rather critical piece of runtime infrastructure was added by Ricardo - the ability to recover gracefully from a kernel crash. 3. 5 backports The backports were Stefan Stanacar's work to add gummiboot and gnu-efi recipes from poky, along with the iasl recipe imported from the meta-virtualization layer. 4. 1 revert Unfortunately the CHIPSEC test suite is not ready to deployed by default because of issues I hit when trying it on one of the machines in my lab, https://github.com/01org/luv-yocto/issues/7. Hopefully this can be resolved for -rc3. The git shortlog looks like this, Matt Fleming (9): recipes-bsp: Add efilinux recipe iasl: New recipe for ACPICA toolchain ovmf: Add iasl as a native dependency generate-manifest-2.7.py: Add importlib chipsec: Add recipe for CHIPSEC v1.1.0 chipsec: Enable luv test automatic execution luv-test: Add auto-generated test files to FILES_${PN} core-image-efi-initramfs: Add chipsec test Revert "core-image-efi-initramfs: Add chipsec test" Ricardo Neri (7): luv-live-image: Create second partition for test results luv-test-manager: Save results to non-volatile media bootimg.bbclass: Add parameter to specify HDDIMG volume ID luv-live-image: Set the volume-id for the boot vfat partition luv-live-image: Append kernel parameter for handling crashes linux-yocto-efi-test: Enable kernel debug info initscritpts: Add a crash handler Stefan Stanacar (4): recipes-bsp: add gnu-efi recipe recipes-bsp: Add gummiboot recipe bootimg/grub-efi.bbclass: allow using a different class for EFI images classes: Add gummiboot class -- Matt Fleming, Intel Open Source Technology Center

7 years, 7 months

1
0
0 / 0

[PATCH 0/2] Save test results to non-volatile media

by Ricardo Neri

Hi, It is useful to have the funciontality of saving the results of the test suites on a non-volatile device. For instance, the results can be analyzed on a development system or fed to a data base. These two patches save the results of the test suites to a non-volatile writable media (e.g., a USB memory stick). In addition to the test results summary, for every test suite, the raw and parsed results are saved. The test results are not saved on the boot partition but on a second partition created for that purpose. TODO: The results partition is mounted using its UUID. Thus, the UUID must be specified in the test manager script and it must match the UUID used when creating the partition. In other words, the UUID must be maintained in two places. If not done diligently, this situation can lead to runtime errors (i.e., not being able to mount the partition). A single UUID should be used in both places... and should be dynamic. Thanks and BR, Ricardo Neri (2): luv-live-image: Create second partition for test results luv-test-manager: Save results to non-volatile media meta-luv/recipes-core/images/luv-live-image.bb | 27 ++++++++++- .../initscripts/initscripts/luv-test-manager | 53 ++++++++++++++++++++-- 2 files changed, 74 insertions(+), 6 deletions(-) -- 1.8.3.2

7 years, 7 months

2
9
0 / 0

[PATCH 0/5] Add CHIPSEC recipe

by Matt Fleming

From: Matt Fleming <matt.fleming(a)intel.com> CHIPSEC is a framework for analyzing security of PC platforms including hardware, system firmware including BIOS/UEFI and the configuration of platform components. It allows creating security test suite, security assessment tools for various low level components and interfaces as well as forensic capabilities for firmware. This series adds a recipe for version v1.1.0 of the upstream project, including the necesary luv-test parser to integrate properly into the testing infrastructure. Matt Fleming (5): generate-manifest-2.7.py: Add importlib chipsec: Add recipe for CHIPSEC v1.1.0 chipsec: Enable luv test automatic execution luv-test: Add auto-generated test files to FILES_${PN} core-image-efi-initramfs: Add chipsec test meta-luv/classes/luv-test.bbclass | 2 +- .../0001-helper-linux-Use-CC-instead-of-cc.patch | 35 ++++++++++ ...02-helper-linux-Allow-INC-to-be-overidden.patch | 26 +++++++ ...n.py-Remove-absolute-reference-to-python-.patch | 29 ++++++++ ...py-Delete-Windows-drivers-from-data_files.patch | 30 ++++++++ meta-luv/recipes-core/chipsec/chipsec/chipsec | 14 ++++ .../chipsec/chipsec/luv-parser-chipsec | 32 +++++++++ meta-luv/recipes-core/chipsec/chipsec_git.bb | 80 ++++++++++++++++++++++ .../images/core-image-efi-initramfs.bb | 2 +- .../python/python-2.7-manifest.inc | 13 ++-- scripts/contrib/python/generate-manifest-2.7.py | 3 + 11 files changed, 259 insertions(+), 7 deletions(-) create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0001-helper-linux-Use-CC-instead-of-cc.patch create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0002-helper-linux-Allow-INC-to-be-overidden.patch create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0003-chipsec_main.py-Remove-absolute-reference-to-python-.patch create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0005-tool-setup.py-Delete-Windows-drivers-from-data_files.patch create mode 100644 meta-luv/recipes-core/chipsec/chipsec/chipsec create mode 100644 meta-luv/recipes-core/chipsec/chipsec/luv-parser-chipsec create mode 100644 meta-luv/recipes-core/chipsec/chipsec_git.bb -- 1.9.0

7 years, 7 months

1
5
0 / 0

[PATCH 0/2] Import iasl recipe from meta-virtualization

by Matt Fleming

From: Matt Fleming <matt.fleming(a)intel.com> Building ovmf currently relies on the host machines having the iasl package installed. We should really be providing all the dependencies for ovmf ourselves instead of requiring packages to be installed on the host machine. Import the iasl recipe from the meta-virtualization layer and add it as a dependency to the ovmf recipe. Matt Fleming (2): iasl: New recipe for ACPICA toolchain ovmf: Add iasl as a native dependency meta-luv/recipes-core/ovmf/ovmf_git.bb | 10 ++++++++- meta-luv/recipes-extended/iasl/iasl_20120215.bb | 27 +++++++++++++++++++++++++ 2 files changed, 36 insertions(+), 1 deletion(-) create mode 100644 meta-luv/recipes-extended/iasl/iasl_20120215.bb -- 1.9.0

7 years, 7 months

1
2
0 / 0

2022

2021

2020

2019

2018

2017

2016

2015

2014

Luv June 2014