[PATCH 2/2] linux-yocto-efi-test: Update linux-libc-headers
by Megha Dey
Since we are updating the kernel LUV uses to v4.12, it is imperative
that we update the linux-libc-headers as well.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
meta-luv/conf/distro/luv.conf | 2 +-
.../recipes-kernel/linux-libc-headers/linux-libc-headers_4.11.bb | 6 ------
.../recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb | 6 ++++++
3 files changed, 7 insertions(+), 7 deletions(-)
delete mode 100644 meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.11.bb
create mode 100644 meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb
diff --git a/meta-luv/conf/distro/luv.conf b/meta-luv/conf/distro/luv.conf
index 09a05cd..55c1d80 100644
--- a/meta-luv/conf/distro/luv.conf
+++ b/meta-luv/conf/distro/luv.conf
@@ -4,7 +4,7 @@ DISTRO_VERSION = "2.1-dev"
TCLIBCAPPEND = ""
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-efi-test"
-LINUXLIBCVERSION = "4.11"
+LINUXLIBCVERSION = "4.12"
LAYER_CONF_VERSION ?= "6"
diff --git a/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.11.bb b/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.11.bb
deleted file mode 100644
index 3b59c1a..0000000
--- a/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.11.bb
+++ /dev/null
@@ -1,6 +0,0 @@
-require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
-
-FILESEXTRAPATHS_prepend :="../../../meta/recipes-kernel/linux-libc-headers:"
-
-SRC_URI[md5sum] = "251a5deee0fa6daf3f356b1bbda9eab8"
-SRC_URI[sha256sum] = "b67ecafd0a42b3383bf4d82f0850cbff92a7e72a215a6d02f42ddbafcf42a7d6"
diff --git a/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb b/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb
new file mode 100644
index 0000000..7bb4aeb
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux-libc-headers/linux-libc-headers_4.12.bb
@@ -0,0 +1,6 @@
+require recipes-kernel/linux-libc-headers/linux-libc-headers.inc
+
+FILESEXTRAPATHS_prepend :="../../../meta/recipes-kernel/linux-libc-headers:"
+
+SRC_URI[md5sum] = "fc454157e2d024d401a60905d6481c6b"
+SRC_URI[sha256sum] = "a45c3becd4d08ce411c14628a949d08e2433d8cdeca92036c7013980e93858ab"
--
1.9.1
4 years, 2 months
[PATCH 1/2] linux-yocto-efi-test: Update recipe for Linux v4.12
by Megha Dey
Update LINUX_VERSION, SRC_REV recipe name and defconfig for Linux
v4.12.
Also, remove
0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch and
0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
as this has already been merged in v4.12.
Signed-off-by: Megha Dey <megha.dey(a)linux.intel.com>
---
...-generating-invalid-ThunderX2-DMA-aliases.patch | 73 ----------
...vice-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch | 62 ---------
.../linux/linux-yocto-efi-test_4.11.bb | 149 ---------------------
.../linux/linux-yocto-efi-test_4.12.bb | 147 ++++++++++++++++++++
4 files changed, 147 insertions(+), 284 deletions(-)
delete mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
delete mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
delete mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.12.bb
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
deleted file mode 100644
index bdda0e2..0000000
--- a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
+++ /dev/null
@@ -1,73 +0,0 @@
-From 545a8e543ad0e5aa42a3c5f1a7d6132e11e3e7ba Mon Sep 17 00:00:00 2001
-From: Jayachandran C <jnair(a)caviumnetworks.com>
-Date: Thu, 13 Apr 2017 20:30:45 +0000
-Subject: [PATCH] PCI: Avoid generating invalid ThunderX2 DMA aliases
-
-On Cavium ThunderX2 arm64 SoCs (formerly known as Broadcom Vulcan), the PCI
-topology is slightly unusual. For a multi-node system, it looks like:
-
- 00:00.0 PCI bridge to [bus 01-1e]
- 01:0a.0 PCI-to-PCIe bridge to [bus 02-04]
- 02:00.0 PCIe Root Port bridge to [bus 03-04] (XLATE_ROOT)
- 03:00.0 PCIe Endpoint
-
-pci_for_each_dma_alias() assumes IOMMU translation is done at the root of
-the PCI hierarchy. It generates 03:00.0, 01:0a.0, and 00:00.0 as DMA
-aliases for 03:00.0 because buses 01 and 00 are non-PCIe buses that don't
-carry the Requester ID.
-
-Because the ThunderX2 IOMMU is at 02:00.0, the Requester IDs 01:0a.0 and
-00:00.0 are never valid for the endpoint. This quirk stops alias
-generation at the XLATE_ROOT bridge so we won't generate 01:0a.0 or
-00:00.0.
-
-The current IOMMU code only maps the last alias (this is a separate bug in
-itself). Prior to this quirk, we only created IOMMU mappings for the
-invalid Requester ID 00:00:0, which never matched any DMA transactions.
-
-With this quirk, we create IOMMU mappings for a valid Requester ID, which
-fixes devices with no aliases but leaves devices with aliases still broken.
-
-The last alias for the endpoint is also used by the ARM GICv3 MSI-X code.
-Without this quirk, the GIC Interrupt Translation Tables are setup with the
-invalid Requester ID, and the MSI-X generated by the device fails to be
-translated and routed.
-
-Link: https://bugzilla.kernel.org/show_bug.cgi?id=195447
-Signed-off-by: Jayachandran C <jnair(a)caviumnetworks.com>
-Signed-off-by: Bjorn Helgaas <bhelgaas(a)google.com>
-Reviewed-by: Robin Murphy <robin.murphy(a)arm.com>
-Acked-by: David Daney <david.daney(a)cavium.com>
-(cherry picked from commit 45a2329367386342d41ea9414c88b023f5a79055)
----
- drivers/pci/quirks.c | 14 ++++++++++++++
- 1 file changed, 14 insertions(+)
-
-diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
-index 6736836..96d3329 100644
---- a/drivers/pci/quirks.c
-+++ b/drivers/pci/quirks.c
-@@ -3958,6 +3958,20 @@ static void quirk_mic_x200_dma_alias(struct pci_dev *pdev)
- DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2264, quirk_mic_x200_dma_alias);
-
- /*
-+ * The IOMMU and interrupt controller on Broadcom Vulcan/Cavium ThunderX2 are
-+ * associated not at the root bus, but at a bridge below. This quirk avoids
-+ * generating invalid DMA aliases.
-+ */
-+static void quirk_bridge_cavm_thrx2_pcie_root(struct pci_dev *pdev)
-+{
-+ pdev->dev_flags |= PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT;
-+}
-+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9000,
-+ quirk_bridge_cavm_thrx2_pcie_root);
-+DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9084,
-+ quirk_bridge_cavm_thrx2_pcie_root);
-+
-+/*
- * Intersil/Techwell TW686[4589]-based video capture cards have an empty (zero)
- * class code. Fix it.
- */
---
-1.8.3.1
-
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
deleted file mode 100644
index 10534f6..0000000
--- a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
+++ /dev/null
@@ -1,62 +0,0 @@
-From 535201f415cc11a8d2caebe2dedfd52d142addae Mon Sep 17 00:00:00 2001
-From: Jayachandran C <jnair(a)caviumnetworks.com>
-Date: Thu, 13 Apr 2017 20:30:44 +0000
-Subject: [PATCH] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT
-
-Add a new quirk flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT to limit the DMA alias
-search to go no further than the bridge where the IOMMU unit is attached.
-
-The flag will be used to indicate a bridge device which forwards the
-address translation requests to the IOMMU, i.e., where the interrupt and
-DMA requests leave the PCIe hierarchy and go into the system blocks.
-
-Usually this happens at the PCI RC, so this flag is not needed. But on
-systems where there are bridges that introduce aliases above the IOMMU,
-this flag prevents pci_for_each_dma_alias() from generating aliases that
-the IOMMU will never see.
-
-The function pci_for_each_dma_alias() is updated to stop when it see a
-bridge with this flag set.
-
-Link: https://bugzilla.kernel.org/show_bug.cgi?id=195447
-Signed-off-by: Jayachandran C <jnair(a)caviumnetworks.com>
-Signed-off-by: Bjorn Helgaas <bhelgaas(a)google.com>
-Reviewed-by: Robin Murphy <robin.murphy(a)arm.com>
-Acked-by: David Daney <david.daney(a)cavium.com>
-(cherry picked from commit ffff885832101543c002cef7abcab0fd27a9aee1)
----
- drivers/pci/search.c | 4 ++++
- include/linux/pci.h | 2 ++
- 2 files changed, 6 insertions(+)
-
-diff --git a/drivers/pci/search.c b/drivers/pci/search.c
-index 33e0f03..4c6044a 100644
---- a/drivers/pci/search.c
-+++ b/drivers/pci/search.c
-@@ -60,6 +60,10 @@ int pci_for_each_dma_alias(struct pci_dev *pdev,
-
- tmp = bus->self;
-
-+ /* stop at bridge where translation unit is associated */
-+ if (tmp->dev_flags & PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT)
-+ return ret;
-+
- /*
- * PCIe-to-PCI/X bridges alias transactions from downstream
- * devices using the subordinate bus number (PCI Express to
-diff --git a/include/linux/pci.h b/include/linux/pci.h
-index eb3da1a..3f596ac 100644
---- a/include/linux/pci.h
-+++ b/include/linux/pci.h
-@@ -178,6 +178,8 @@ enum pci_dev_flags {
- PCI_DEV_FLAGS_NO_PM_RESET = (__force pci_dev_flags_t) (1 << 7),
- /* Get VPD from function 0 VPD */
- PCI_DEV_FLAGS_VPD_REF_F0 = (__force pci_dev_flags_t) (1 << 8),
-+ /* a non-root bridge where translation occurs, stop alias search here */
-+ PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT = (__force pci_dev_flags_t) (1 << 9),
- };
-
- enum pci_irq_reroute_variant {
---
-1.8.3.1
-
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
deleted file mode 100644
index 3af0851..0000000
--- a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
+++ /dev/null
@@ -1,149 +0,0 @@
-# linux-yocto-custom.bb:
-#
-# An example kernel recipe that uses the linux-yocto and oe-core
-# kernel classes to apply a subset of yocto kernel management to git
-# managed kernel repositories.
-#
-# To use linux-yocto-custom in your layer, create a
-# linux-yocto-custom.bbappend file containing at least the following
-# lines:
-#
-# FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-# COMPATIBLE_MACHINE_yourmachine = "yourmachine"
-#
-# You must also provide a Linux kernel configuration. The most direct
-# method is to copy your .config to files/defconfig in your layer,
-# in the same directory as the bbappend and add file://defconfig to
-# your SRC_URI.
-#
-# To use the yocto kernel tooling to generate a BSP configuration
-# using modular configuration fragments, see the yocto-bsp and
-# yocto-kernel tools documentation.
-#
-# Warning:
-#
-# Building this example without providing a defconfig or BSP
-# configuration will result in build or boot errors. This is not a
-# bug.
-#
-#
-# Notes:
-#
-# patches: patches can be merged into to the source git tree itself,
-# added via the SRC_URI, or controlled via a BSP
-# configuration.
-#
-# defconfig: When a defconfig is provided, the linux-yocto configuration
-# uses the filename as a trigger to use a 'allnoconfig' baseline
-# before merging the defconfig into the build.
-#
-# If the defconfig file was created with make_savedefconfig,
-# not all options are specified, and should be restored with their
-# defaults, not set to 'n'. To properly expand a defconfig like
-# this, specify: KCONFIG_MODE="--alldefconfig" in the kernel
-# recipe.
-#
-# example configuration addition:
-# SRC_URI += "file://smp.cfg"
-# example patch addition (for kernel v3.4 only):
-# SRC_URI += "file://0001-linux-version-tweak.patch
-# example feature addition (for kernel v3.4 only):
-# SRC_URI += "file://feature.scc"
-#
-
-KBRANCH="master"
-inherit kernel
-require recipes-kernel/linux/linux-yocto.inc
-
-KERNEL_FEATURES_remove= " features/debug/printk.scc"
-
-# Override SRC_URI in a bbappend file to point at a different source
-# tree if you do not want to build from Linus' tree.
-SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol..."
-
-# These patches are under discussion on ML
-SRC_URI += "file://0001-serial-SPCR-check-bit-width-for-the-16550-UART.patch \
- "
-
-# Detect illegal accesses to EFI regions (like EFI_CONVENTIONAL_MEMORY,
-# EFI_LOADER_CODE/DATA, EFI_BOOT_SERVICES_CODE/DATA) by firmware.
-SRC_URI += "file://0001-x86-mm-Allocate-pages-without-sleeping.patch \
- file://0002-x86-efi-remove-__init-attribute-from-memory-mapping-.patch \
- file://0003-x86-efi-Save-EFI_MEMORY_MAP-passed-by-firmware-perma.patch \
- file://0004-x86-efi-Copy-support-functions-to-install-uninstall-.patch \
- file://0005-efi-Allow-efi_mem_desc_lookup-find-illegally-accesse.patch \
- file://0006-x86-efi-Add-function-to-fixup-page-faults-in-illegal.patch \
- file://0007-x86-efi-Fixup-faults-from-UEFI-firmware.patch \
- file://0008-x86-efi-Introduce-EFI_WARN_ON_ILLEGAL_ACCESSES.patch \
- file://0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch \
- file://0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch \
- file://0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch \
- file://0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch \
- "
-
-COMMON_CFG_x86 = " file://qemux86/modules.cfg \
- file://qemux86/display.cfg \
- file://qemux86/ram_block.cfg \
- file://qemux86/debug.cfg \
- file://qemux86/efi_x86.cfg \
- file://qemux86/usb_hcd.cfg \
- file://qemux86/network.cfg \
- file://qemux86/network-devices.cfg \
- file://qemux86/usb_ethernet.cfg \
- "
-
-# Add the kernel configuration fragments for x86/x86-64/arm64
-SRC_URI_append_x86 = "${COMMON_CFG_x86} \
- file://qemux86/highmem.cfg \
- "
-SRC_URI_append_x86-64 = "${COMMON_CFG_x86} \
- file://qemux86/ndctl.cfg \
- file://qemux86-64/efi_x86-64.cfg \
- file://qemux86-64/linux_quirks.cfg \
- "
-SRC_URI_append_aarch64 = " file://qemuarm64/network.cfg \
- file://qemuarm64/sbbr.cfg \
- "
-
-# pstore, highmem and efi configs are common to all the supported architectures
-SRC_URI_append = "file://pstore.cfg \
- file://efi.cfg \
- "
-
-# Override KCONFIG_MODE to '--alldefconfig' from the default '--allnoconfig'
-KCONFIG_MODE = 'alldefconfig'
-
-# If a defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it
-# from the source tree, into a common location and normalized "defconfig" name,
-# where the rest of the process will include and incoroporate it into the build
-
-# If the fetcher has already placed a defconfig in WORKDIR (from the SRC_URI),
-# we don't overwrite it, but instead warn the user that SRC_URI defconfigs take
-# precendence.
-KBUILD_DEFCONFIG = "defconfig"
-KBUILD_DEFCONFIG_x86 = "i386_defconfig"
-KBUILD_DEFCONFIG_x86-64 = "x86_64_defconfig"
-LINUX_VERSION ?= "4.11"
-LINUX_VERSION_EXTENSION ?= "-efitest"
-
-# Override SRCREV to point to a different commit in a bbappend file to
-# build a different release of the Linux kernel.
-# tag: v4.11 a351e9b9fc24e982ec2f0e76379a49826036da12
-SRCREV = "a351e9b9fc24e982ec2f0e76379a49826036da12"
-
-PR = "r5"
-PV = "${LINUX_VERSION}+git${SRCPV}"
-
-# Override COMPATIBLE_MACHINE to include your machine in a bbappend
-# file. Leaving it empty here ensures an early explicit build failure.
-COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm64"
-
-do_install_append() {
- if [ "${TARGET_ARCH}" = "x86_64" ]; then
- # There are 2 copies of the NVDIMM modules which are built. This is a
- # temporary fix to make sure the correct set of modules are used.
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/nvdimm/
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/dax/
- rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/acpi/
- fi
-}
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.12.bb b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.12.bb
new file mode 100644
index 0000000..16d3a2e
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.12.bb
@@ -0,0 +1,147 @@
+# linux-yocto-custom.bb:
+#
+# An example kernel recipe that uses the linux-yocto and oe-core
+# kernel classes to apply a subset of yocto kernel management to git
+# managed kernel repositories.
+#
+# To use linux-yocto-custom in your layer, create a
+# linux-yocto-custom.bbappend file containing at least the following
+# lines:
+#
+# FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
+# COMPATIBLE_MACHINE_yourmachine = "yourmachine"
+#
+# You must also provide a Linux kernel configuration. The most direct
+# method is to copy your .config to files/defconfig in your layer,
+# in the same directory as the bbappend and add file://defconfig to
+# your SRC_URI.
+#
+# To use the yocto kernel tooling to generate a BSP configuration
+# using modular configuration fragments, see the yocto-bsp and
+# yocto-kernel tools documentation.
+#
+# Warning:
+#
+# Building this example without providing a defconfig or BSP
+# configuration will result in build or boot errors. This is not a
+# bug.
+#
+#
+# Notes:
+#
+# patches: patches can be merged into to the source git tree itself,
+# added via the SRC_URI, or controlled via a BSP
+# configuration.
+#
+# defconfig: When a defconfig is provided, the linux-yocto configuration
+# uses the filename as a trigger to use a 'allnoconfig' baseline
+# before merging the defconfig into the build.
+#
+# If the defconfig file was created with make_savedefconfig,
+# not all options are specified, and should be restored with their
+# defaults, not set to 'n'. To properly expand a defconfig like
+# this, specify: KCONFIG_MODE="--alldefconfig" in the kernel
+# recipe.
+#
+# example configuration addition:
+# SRC_URI += "file://smp.cfg"
+# example patch addition (for kernel v3.4 only):
+# SRC_URI += "file://0001-linux-version-tweak.patch
+# example feature addition (for kernel v3.4 only):
+# SRC_URI += "file://feature.scc"
+#
+
+KBRANCH="master"
+inherit kernel
+require recipes-kernel/linux/linux-yocto.inc
+
+KERNEL_FEATURES_remove= " features/debug/printk.scc"
+
+# Override SRC_URI in a bbappend file to point at a different source
+# tree if you do not want to build from Linus' tree.
+SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git;protocol..."
+
+# These patches are under discussion on ML
+SRC_URI += "file://0001-serial-SPCR-check-bit-width-for-the-16550-UART.patch \
+ "
+
+# Detect illegal accesses to EFI regions (like EFI_CONVENTIONAL_MEMORY,
+# EFI_LOADER_CODE/DATA, EFI_BOOT_SERVICES_CODE/DATA) by firmware.
+SRC_URI += "file://0001-x86-mm-Allocate-pages-without-sleeping.patch \
+ file://0002-x86-efi-remove-__init-attribute-from-memory-mapping-.patch \
+ file://0003-x86-efi-Save-EFI_MEMORY_MAP-passed-by-firmware-perma.patch \
+ file://0004-x86-efi-Copy-support-functions-to-install-uninstall-.patch \
+ file://0005-efi-Allow-efi_mem_desc_lookup-find-illegally-accesse.patch \
+ file://0006-x86-efi-Add-function-to-fixup-page-faults-in-illegal.patch \
+ file://0007-x86-efi-Fixup-faults-from-UEFI-firmware.patch \
+ file://0008-x86-efi-Introduce-EFI_WARN_ON_ILLEGAL_ACCESSES.patch \
+ file://0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch \
+ file://0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch \
+ "
+
+COMMON_CFG_x86 = " file://qemux86/modules.cfg \
+ file://qemux86/display.cfg \
+ file://qemux86/ram_block.cfg \
+ file://qemux86/debug.cfg \
+ file://qemux86/efi_x86.cfg \
+ file://qemux86/usb_hcd.cfg \
+ file://qemux86/network.cfg \
+ file://qemux86/network-devices.cfg \
+ file://qemux86/usb_ethernet.cfg \
+ "
+
+# Add the kernel configuration fragments for x86/x86-64/arm64
+SRC_URI_append_x86 = "${COMMON_CFG_x86} \
+ file://qemux86/highmem.cfg \
+ "
+SRC_URI_append_x86-64 = "${COMMON_CFG_x86} \
+ file://qemux86/ndctl.cfg \
+ file://qemux86-64/efi_x86-64.cfg \
+ file://qemux86-64/linux_quirks.cfg \
+ "
+SRC_URI_append_aarch64 = " file://qemuarm64/network.cfg \
+ file://qemuarm64/sbbr.cfg \
+ "
+
+# pstore, highmem and efi configs are common to all the supported architectures
+SRC_URI_append = "file://pstore.cfg \
+ file://efi.cfg \
+ "
+
+# Override KCONFIG_MODE to '--alldefconfig' from the default '--allnoconfig'
+KCONFIG_MODE = 'alldefconfig'
+
+# If a defconfig is specified via the KBUILD_DEFCONFIG variable, we copy it
+# from the source tree, into a common location and normalized "defconfig" name,
+# where the rest of the process will include and incoroporate it into the build
+
+# If the fetcher has already placed a defconfig in WORKDIR (from the SRC_URI),
+# we don't overwrite it, but instead warn the user that SRC_URI defconfigs take
+# precendence.
+KBUILD_DEFCONFIG = "defconfig"
+KBUILD_DEFCONFIG_x86 = "i386_defconfig"
+KBUILD_DEFCONFIG_x86-64 = "x86_64_defconfig"
+LINUX_VERSION ?= "4.12"
+LINUX_VERSION_EXTENSION ?= "-efitest"
+
+# Override SRCREV to point to a different commit in a bbappend file to
+# build a different release of the Linux kernel.
+# tag: v4.12 6f7da290413ba713f0cdd9ff1a2a9bb129ef4f6c
+SRCREV = "6f7da290413ba713f0cdd9ff1a2a9bb129ef4f6c"
+
+PR = "r5"
+PV = "${LINUX_VERSION}+git${SRCPV}"
+
+# Override COMPATIBLE_MACHINE to include your machine in a bbappend
+# file. Leaving it empty here ensures an early explicit build failure.
+COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm64"
+
+do_install_append() {
+ if [ "${TARGET_ARCH}" = "x86_64" ]; then
+ # There are 2 copies of the NVDIMM modules which are built. This is a
+ # temporary fix to make sure the correct set of modules are used.
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/nvdimm/
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/dax/
+ rm -rf ${D}/lib/modules/${LINUX_VERSION}.0-yocto-standard/kernel/drivers/acpi/
+ fi
+}
--
1.9.1
4 years, 2 months
Firmware Test Suite 17.07.00 is released
by Alex Hung
FWTS 17.07.00 is released.
It is available from:
Tar: http://fwts.ubuntu.com/release/fwts-V17.07.00.tar.gz
PPA: https://launchpad.net/~firmware-testing-team/+archive/ubuntu/ppa-fwts-stable
Release notes: https://wiki.ubuntu.com/FirmwareTestSuite/ReleaseNotes/17.07.00
= New Features =
* acpi: bgrt: update according to acpi 6.1 errata (mantis 1577)
* acpi: method: update _PSD and _TSD tests according to ACPI 6.1 errata
* acpi: rsdp: revision 1 must have length 20 according to ACPI 6.1 errata
* acpi: method: Add _CPC revision 3 according to ACPI 6.2 (mantis 1611)
* acpi: hest: add new type 11 introduced in ACPI 6.2 (mantis 1649)
* acpi: srat: add new type 4 according to ACPI 6.2 (mantis 1656)
* acpi: method: update _GCP according to ACPI 6.2 (mantis 1703)
* acpi: hest: add notification type 11 according to ACPI 6.2 (mantis 1731)
* acpi: fadt: update minor version to 2 for ACPI 6.2 (mantis 1769)
* acpi: hest: add checks for GHES_ASSIST flag value in ACPI 6.2 (mantis 1674)
* acpi: wsmt: add wsmt test according to ACPI 6.2 (mantis 1585)
* ACPICA: Update to version 20170629
* acpi: tpm2: Add additional start method values
* acpi: iort: Add PMCG support
= Fixed Bugs =
* acpi: hest: change type from hex to dec as in ACPI spec
* acpi: hest: change a function name to meet the patterns of others
* acpi: hest: fix typo for type 7
* dmi: dmicheck: ensure mmap'd SMBIOS data is readable before accessing it
* bios32: ensure mmap'd memory is readable before accessing it
* bios: ebdadump: ensure mmap'd memory is readable before accessing it
* bios: romdump: ensure mmap'd memory is readable before accessing it
* lib: fwts_smbios: ensure mmap'd memory is readable before accessing it
* efi_runtime: Use memdup_user helper
= Detail Changelog =
To check /usr/share/doc/fwts/changelog.Debian.gz or
fwts_17.07.00-0ubuntu1.debian.tar.gz from
https://launchpad.net/ubuntu/+source/fwts
4 years, 3 months
[PATCH] fwts: bump to v17.07.00
by Naresh Bhat
Update FWTS to version v17.07.00
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
meta-luv/recipes-core/fwts/fwts_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-luv/recipes-core/fwts/fwts_git.bb b/meta-luv/recipes-core/fwts/fwts_git.bb
index c2ae628..5011aca 100644
--- a/meta-luv/recipes-core/fwts/fwts_git.bb
+++ b/meta-luv/recipes-core/fwts/fwts_git.bb
@@ -4,9 +4,9 @@ HOMEPAGE = "https://wiki.ubuntu.com/Kernel/Reference/fwts"
LICENSE = "GPLv2+"
LIC_FILES_CHKSUM = "file://src/main.c;beginline=1;endline=16;md5=31da590f3e9f3bd34dcdb9e4db568519"
-PV = "V17.06.00+git${SRCPV}"
+PV = "V17.07.00+git${SRCPV}"
-SRCREV = "ed47ce1c27db7a398613ab61fde2aa747d312134"
+SRCREV = "215a0b5b5c5b3b54bd7ef654429b5645f17906fa"
SRC_URI = "git://kernel.ubuntu.com/hwe/fwts.git \
file://luv-parser-fwts \
"
--
2.7.4
4 years, 3 months
[PATCH] linux-yocto-efi-test: Add ThunderX2 missing patch
by Naresh Bhat
The set of patches are required on top of v4.11 kernel to
boot the LUV on Cavium ThunderX2 T99xx hardware.
The patches #1 and #2 are already merged into v4.12 kernel
Hence please ignore them when you bump the kernel to v4.12
Signed-off-by: Naresh Bhat <naresh.bhat(a)linaro.org>
---
...AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch | 55 ++++++++++++++++
...rx2-Fix-for-errata-that-affects-stop-engi.patch | 62 ++++++++++++++++++
...-generating-invalid-ThunderX2-DMA-aliases.patch | 73 ++++++++++++++++++++++
...vice-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch | 62 ++++++++++++++++++
.../linux/linux-yocto-efi-test_4.11.bb | 4 ++
5 files changed, 256 insertions(+)
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
create mode 100644 meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch
new file mode 100644
index 0000000..f730b7b
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch
@@ -0,0 +1,55 @@
+From 3e286835347cfbe01fca80496f4c767c2bdc2094 Mon Sep 17 00:00:00 2001
+From: Ashok Kumar Sekar <asekar(a)redhat.com>
+Date: Fri, 23 Sep 2016 04:16:19 -0700
+Subject: [PATCH 1/2] PCI: Vulcan: AHCI PCI bar fix for Broadcom Vulcan early
+ silicon
+
+PCI BAR 5 is not setup correctly for the on-board AHCI
+controller on Broadcom's Vulcan processor. Added a quirk to fix BAR 5
+by using BAR 4's resources which are populated correctly but NOT used
+by the AHCI controller actually.
+
+Signed-off-by: Ashok Kumar Sekar <asekar(a)redhat.com>
+Signed-off-by: Jayachandran C <jchandra(a)broadcom.com>
+---
+ drivers/pci/quirks.c | 24 ++++++++++++++++++++++++
+ 1 file changed, 24 insertions(+)
+
+diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
+index 6736836..4565800 100644
+--- a/drivers/pci/quirks.c
++++ b/drivers/pci/quirks.c
+@@ -3958,6 +3958,30 @@ static void quirk_mic_x200_dma_alias(struct pci_dev *pdev)
+ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2264, quirk_mic_x200_dma_alias);
+
+ /*
++ * PCI BAR 5 is not setup correctly for the on-board AHCI controller
++ * on Broadcom's Vulcan processor. Added a quirk to fix BAR 5 by
++ * using BAR 4's resources which are populated correctly and NOT
++ * actually used by the AHCI controller.
++ */
++static void quirk_fix_vulcan_ahci_bars(struct pci_dev *dev)
++{
++ struct resource *r = &dev->resource[4];
++
++ if (!(r->flags & IORESOURCE_MEM) || (r->start == 0))
++ return;
++
++ /* Set BAR5 resource to BAR4 */
++ dev->resource[5] = *r;
++
++ /* Update BAR5 in pci config space */
++ pci_write_config_dword(dev, PCI_BASE_ADDRESS_5, r->start);
++
++ /* Clear BAR4's resource */
++ memset(r, 0, sizeof(*r));
++}
++DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9027, quirk_fix_vulcan_ahci_bars);
++
++/*
+ * Intersil/Techwell TW686[4589]-based video capture cards have an empty (zero)
+ * class code. Fix it.
+ */
+--
+1.8.3.1
+
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch
new file mode 100644
index 0000000..7575940
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch
@@ -0,0 +1,62 @@
+From 6d1feb1fccc3bdf99364ed83e950a70b3c2d7963 Mon Sep 17 00:00:00 2001
+From: Jayachandran C <jnair(a)caviumnetworks.com>
+Date: Fri, 10 Mar 2017 10:04:52 +0000
+Subject: [PATCH 2/2] ahci: thunderx2: Fix for errata that affects stop engine
+
+Apply workaround for this errata:
+ Synopsis: Resetting PxCMD.ST may hang the SATA device
+
+ Description: An internal ping-pong buffer state is not reset
+ correctly for an PxCMD.ST=0 command for a SATA channel. This
+ may cause the SATA interface to hang when a PxCMD.ST=0 command
+ is received.
+
+ Workaround: A SATA_BIU_CORE_ENABLE.sw_init_bsi must be asserted
+ by the driver whenever the PxCMD.ST needs to be de-asserted. This
+ will reset both the ports. So, it may not always work in a 2
+ channel SATA system.
+
+ Resolution: Fix in B0.
+
+Add the code to ahci_stop_engine() to do this. It is not easy to
+stop the other "port" since it is associated with a different AHCI
+interface. Please note that with this fix, SATA reset does not
+hang any more, but it can cause failures on the other interface
+if that is in active use.
+
+Unfortunately, we have nothing other the the CPU ID to check if the
+SATA block has this issue.
+
+Signed-off-by: Jayachandran C <jnair(a)caviumnetworks.com>
+---
+ drivers/ata/libahci.c | 14 ++++++++++++++
+ 1 file changed, 14 insertions(+)
+
+diff --git a/drivers/ata/libahci.c b/drivers/ata/libahci.c
+index 3159f9e..5f64275 100644
+--- a/drivers/ata/libahci.c
++++ b/drivers/ata/libahci.c
+@@ -664,6 +664,20 @@ int ahci_stop_engine(struct ata_port *ap)
+ tmp &= ~PORT_CMD_START;
+ writel(tmp, port_mmio + PORT_CMD);
+
++#ifdef CONFIG_ARM64
++ /* Rev Ax of Cavium CN99XX needs a hack for port stop */
++ if (MIDR_IS_CPU_MODEL_RANGE(read_cpuid_id(),
++ MIDR_CPU_MODEL(ARM_CPU_IMP_BRCM, BRCM_CPU_PART_VULCAN),
++ MIDR_CPU_VAR_REV(0, 0),
++ MIDR_CPU_VAR_REV(0, MIDR_REVISION_MASK))) {
++ tmp = readl(hpriv->mmio + 0x8000);
++ writel(tmp | (1 << 26), hpriv->mmio + 0x8000);
++ udelay(1);
++ writel(tmp & ~(1 << 26), hpriv->mmio + 0x8000);
++ dev_warn(ap->host->dev, "CN99XX stop engine fix applied!\n");
++ }
++#endif
++
+ /* wait for engine to stop. This could be as long as 500 msec */
+ tmp = ata_wait_register(ap, port_mmio + PORT_CMD,
+ PORT_CMD_LIST_ON, PORT_CMD_LIST_ON, 1, 500);
+--
+1.8.3.1
+
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
new file mode 100644
index 0000000..bdda0e2
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch
@@ -0,0 +1,73 @@
+From 545a8e543ad0e5aa42a3c5f1a7d6132e11e3e7ba Mon Sep 17 00:00:00 2001
+From: Jayachandran C <jnair(a)caviumnetworks.com>
+Date: Thu, 13 Apr 2017 20:30:45 +0000
+Subject: [PATCH] PCI: Avoid generating invalid ThunderX2 DMA aliases
+
+On Cavium ThunderX2 arm64 SoCs (formerly known as Broadcom Vulcan), the PCI
+topology is slightly unusual. For a multi-node system, it looks like:
+
+ 00:00.0 PCI bridge to [bus 01-1e]
+ 01:0a.0 PCI-to-PCIe bridge to [bus 02-04]
+ 02:00.0 PCIe Root Port bridge to [bus 03-04] (XLATE_ROOT)
+ 03:00.0 PCIe Endpoint
+
+pci_for_each_dma_alias() assumes IOMMU translation is done at the root of
+the PCI hierarchy. It generates 03:00.0, 01:0a.0, and 00:00.0 as DMA
+aliases for 03:00.0 because buses 01 and 00 are non-PCIe buses that don't
+carry the Requester ID.
+
+Because the ThunderX2 IOMMU is at 02:00.0, the Requester IDs 01:0a.0 and
+00:00.0 are never valid for the endpoint. This quirk stops alias
+generation at the XLATE_ROOT bridge so we won't generate 01:0a.0 or
+00:00.0.
+
+The current IOMMU code only maps the last alias (this is a separate bug in
+itself). Prior to this quirk, we only created IOMMU mappings for the
+invalid Requester ID 00:00:0, which never matched any DMA transactions.
+
+With this quirk, we create IOMMU mappings for a valid Requester ID, which
+fixes devices with no aliases but leaves devices with aliases still broken.
+
+The last alias for the endpoint is also used by the ARM GICv3 MSI-X code.
+Without this quirk, the GIC Interrupt Translation Tables are setup with the
+invalid Requester ID, and the MSI-X generated by the device fails to be
+translated and routed.
+
+Link: https://bugzilla.kernel.org/show_bug.cgi?id=195447
+Signed-off-by: Jayachandran C <jnair(a)caviumnetworks.com>
+Signed-off-by: Bjorn Helgaas <bhelgaas(a)google.com>
+Reviewed-by: Robin Murphy <robin.murphy(a)arm.com>
+Acked-by: David Daney <david.daney(a)cavium.com>
+(cherry picked from commit 45a2329367386342d41ea9414c88b023f5a79055)
+---
+ drivers/pci/quirks.c | 14 ++++++++++++++
+ 1 file changed, 14 insertions(+)
+
+diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c
+index 6736836..96d3329 100644
+--- a/drivers/pci/quirks.c
++++ b/drivers/pci/quirks.c
+@@ -3958,6 +3958,20 @@ static void quirk_mic_x200_dma_alias(struct pci_dev *pdev)
+ DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_INTEL, 0x2264, quirk_mic_x200_dma_alias);
+
+ /*
++ * The IOMMU and interrupt controller on Broadcom Vulcan/Cavium ThunderX2 are
++ * associated not at the root bus, but at a bridge below. This quirk avoids
++ * generating invalid DMA aliases.
++ */
++static void quirk_bridge_cavm_thrx2_pcie_root(struct pci_dev *pdev)
++{
++ pdev->dev_flags |= PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT;
++}
++DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9000,
++ quirk_bridge_cavm_thrx2_pcie_root);
++DECLARE_PCI_FIXUP_HEADER(PCI_VENDOR_ID_BROADCOM, 0x9084,
++ quirk_bridge_cavm_thrx2_pcie_root);
++
++/*
+ * Intersil/Techwell TW686[4589]-based video capture cards have an empty (zero)
+ * class code. Fix it.
+ */
+--
+1.8.3.1
+
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
new file mode 100644
index 0000000..10534f6
--- /dev/null
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test/0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch
@@ -0,0 +1,62 @@
+From 535201f415cc11a8d2caebe2dedfd52d142addae Mon Sep 17 00:00:00 2001
+From: Jayachandran C <jnair(a)caviumnetworks.com>
+Date: Thu, 13 Apr 2017 20:30:44 +0000
+Subject: [PATCH] PCI: Add device flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT
+
+Add a new quirk flag PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT to limit the DMA alias
+search to go no further than the bridge where the IOMMU unit is attached.
+
+The flag will be used to indicate a bridge device which forwards the
+address translation requests to the IOMMU, i.e., where the interrupt and
+DMA requests leave the PCIe hierarchy and go into the system blocks.
+
+Usually this happens at the PCI RC, so this flag is not needed. But on
+systems where there are bridges that introduce aliases above the IOMMU,
+this flag prevents pci_for_each_dma_alias() from generating aliases that
+the IOMMU will never see.
+
+The function pci_for_each_dma_alias() is updated to stop when it see a
+bridge with this flag set.
+
+Link: https://bugzilla.kernel.org/show_bug.cgi?id=195447
+Signed-off-by: Jayachandran C <jnair(a)caviumnetworks.com>
+Signed-off-by: Bjorn Helgaas <bhelgaas(a)google.com>
+Reviewed-by: Robin Murphy <robin.murphy(a)arm.com>
+Acked-by: David Daney <david.daney(a)cavium.com>
+(cherry picked from commit ffff885832101543c002cef7abcab0fd27a9aee1)
+---
+ drivers/pci/search.c | 4 ++++
+ include/linux/pci.h | 2 ++
+ 2 files changed, 6 insertions(+)
+
+diff --git a/drivers/pci/search.c b/drivers/pci/search.c
+index 33e0f03..4c6044a 100644
+--- a/drivers/pci/search.c
++++ b/drivers/pci/search.c
+@@ -60,6 +60,10 @@ int pci_for_each_dma_alias(struct pci_dev *pdev,
+
+ tmp = bus->self;
+
++ /* stop at bridge where translation unit is associated */
++ if (tmp->dev_flags & PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT)
++ return ret;
++
+ /*
+ * PCIe-to-PCI/X bridges alias transactions from downstream
+ * devices using the subordinate bus number (PCI Express to
+diff --git a/include/linux/pci.h b/include/linux/pci.h
+index eb3da1a..3f596ac 100644
+--- a/include/linux/pci.h
++++ b/include/linux/pci.h
+@@ -178,6 +178,8 @@ enum pci_dev_flags {
+ PCI_DEV_FLAGS_NO_PM_RESET = (__force pci_dev_flags_t) (1 << 7),
+ /* Get VPD from function 0 VPD */
+ PCI_DEV_FLAGS_VPD_REF_F0 = (__force pci_dev_flags_t) (1 << 8),
++ /* a non-root bridge where translation occurs, stop alias search here */
++ PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT = (__force pci_dev_flags_t) (1 << 9),
+ };
+
+ enum pci_irq_reroute_variant {
+--
+1.8.3.1
+
diff --git a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
index d9b7112..3af0851 100644
--- a/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
+++ b/meta-luv/recipes-kernel/linux/linux-yocto-efi-test_4.11.bb
@@ -75,6 +75,10 @@ SRC_URI += "file://0001-x86-mm-Allocate-pages-without-sleeping.patch \
file://0006-x86-efi-Add-function-to-fixup-page-faults-in-illegal.patch \
file://0007-x86-efi-Fixup-faults-from-UEFI-firmware.patch \
file://0008-x86-efi-Introduce-EFI_WARN_ON_ILLEGAL_ACCESSES.patch \
+ file://0001-PCI-Vulcan-AHCI-PCI-bar-fix-for-Broadcom-Vulcan-earl.patch \
+ file://0002-ahci-thunderx2-Fix-for-errata-that-affects-stop-engi.patch \
+ file://0003-PCI-Avoid-generating-invalid-ThunderX2-DMA-aliases.patch \
+ file://0004-PCI-Add-device-flag-PCI_DEV_FLAGS_BRIDGE_XLATE_ROOT.patch \
"
COMMON_CFG_x86 = " file://qemux86/modules.cfg \
--
2.7.4
4 years, 3 months
Linux UEFI Validation Project v2.1 release
by Ricardo Neri
Hello,
This is to announce the release of LUV v2.1
Since this release includes mostly bug fixes, stabilization and
fine-tuning updates, it made sense to issue the final release of LUV
v2.1 and start a new release cycle of LUV v2.2.
=== Goodies
Gayatri Kammela won the prize of the most active contributor with many
bug fixes and a new feature. She fixed our netboot image, which was
missing the ramdisk(!). She added support for debugging and logging of
BITS output via network. Likewise, she reworked the LUV configuration
file to make more sense to both humans and computers by making clear
when parameters are not used. She also investigated and fixed
dependencies in systemd that caused delays in the execution of tests.
Lastly, she fixed a couple of build-time bugs.
Naresh Bhat updated our Linux kernel recipe to retrieve the kernel
configuration directly from the source tree rather than manually
updating it. This helped us to remove those eyesore patches for updating
our configuration that needed to be sent every time we bumped to a new
kernel version. The overall result looks great and is closer to the
intended use of the kernel and Yocto Projects's scripts to merge
multiple configuration fragments. I took this opportunity to sanitize
the configuration for x86 to add missing configurations and reorganize
them.
Sai Praneeth Prakhya added functionality to dump relevant and useful
dumps as part of the testing results. Now LUV is capable of dumping the
kernel's boot log, the contents of the ACPI tables as well as the
properties of the CPUs in the system. Very useful! Also, he helped us to
bump to Linux v4.11. He also took burden of rebasing our implementation
to detect firmware's illegal memory access in this new version of Linux.
Matt Hart updated our GRUB configuration to automate boots across all
CPU architectures by not waiting for human intervention to complete
boots.
=== "Nightly" builds
During this release we started publishing our long-promised
nightly-build images. In reality, we issue these images weekly, given
the traffic on the mailing list. For the next release cycle, we will
include in such builds only new versions of test suites and bug fixes.
New features will be released only on official releases.
=== Updated test suites
We include FWTS V17.06.00. CHIPSEC v1.3.1, BITS v2079, and NDCTL v56. We
use Linux v4.11.
=== Binary images for x86
Disk (MBR and GPT partition schemes) and network images for x86 can be
found here:
https://download.01.org/linux-uefi-validation/v2.1/
== Known issues:
* Network issue delays running the testsuites in luv-netboot-image
https://github.com/01org/luv-yocto/issues/124
* luv.reboot not rebooting in LUV v2.1-rc2
https://github.com/01org/luv-yocto/issues/120
* Results are overwritten by horizontal line in luv.html file
https://github.com/01org/luv-yocto/issues/118
* LUV from next branch fails to build on Ubuntu 16.10
https://github.com/01org/luv-yocto/issues/104
* Get rid of License warnings in linux firmware
https://github.com/01org/luv-yocto/issues/103
* sometimes bits-python-native fails to build
https://github.com/01org/luv-yocto/issues/101
* Unstable behavior on i386 images
https://github.com/01org/luv-yocto/issues/76
* Strange error while running live image using qemu
https://github.com/01org/luv-yocto/issues/64
== Fixed issues
* Automate retrieval of Linux defconfig
https://github.com/01org/luv-yocto/issues/116
* Network support in bits
https://github.com/01org/luv-yocto/issues/67
* Add a parser to check for EFI_MEMORY_ATTRIBUTES failure
https://github.com/01org/luv-yocto/issues/110
* Dump boot dmesg into a file
https://github.com/01org/luv-yocto/issues/117
* Kernel panic - not syncing: BIOS has enabled x2apic but kernel
doesn't
https://github.com/01org/luv-yocto/issues/83
* v2.1-rc2 missing from 01.org
https://github.com/01org/luv-yocto/issues/122
=== Short log
Many thanks to all the contributors of this release. This is how the
short log looks like:
Gayatri Kammela (15):
luv-test/luv-test.bb: Add the runtime dependency for gzip utility
luv-net-boot-image.bb: fix the missing initrd
recipes-core/udev: Remove eudev_3.2.bbappend file
recipes-core/: Disable LUV_STORAGE_URL parameter by default in
luv.cfg
modify_luv_netboot_efi.py: Replace the blank space with string
none
recipes-core/images: Remove ip command line parameter from the
image recipes
fwts: bump to v17.05.00
fwts: Include the fix for tests dependency on libfdt
recipe-core/images: Disable LUV_NETCONSOLE parameter by default in
luv.cfg
fwts: bump to v17.06.00
luv-test: fix: Skip luv-crash-handler service while running
luv-netboot image
luv-test: Call luv-netconsole service only if user wants to
configure this feature
luv-test: Skip the check for results partition in
luv-test-manager.service.
bits: Add patch that enables network debug in BITS
meta-luv/README: Update README for netconsole usage in Bits
Matt Hart (1):
luv-efi: Make the grub timeout 0 seconds across all architectures
Megha Dey (1):
luv-test : remove MSG parameter from plymouth_write
Naresh Bhat (3):
linux-yocto-efi-test: Automate retrieval of Linux defconfig
linux-yocto-efi-test: Remove ARM64 defconfig
linux-yocto-efi-test: Remove x86/x86-64 defconfig
Ricardo Neri (12):
chipsec: bump to v1.3.0
linux-yocto-efi-test: x86: use highmem.cfg only in 32-bit builds
linux-yocto-efi-test: x86: network.cfg: sanitize selected options
linux-yocto-efi-test: x86: usb-hcd.cfg: remove support for ISP1760
linux-yocto-efi-test: x86: debug.cfg: add missing options because
of EXPERT
linux-yocto-efi-test: x86: use linux-quirks only in 64-bit builds
linux-yocto-efi-test: pstore.cfg: remove duplicated option
bits: smrr: generalize rules to check address base and range
luv-test: luv-crash-handler: Re-introduce After setting to wait
for disk
chipsec: run CHIPSEC without the -i option
chipsec: bump to v1.3.1
LUV v2.1
Sai Praneeth (14):
kernel-efi-warnings: Check dmesg for errors while parsing
EFI_MEMORY_ATTRIBUTES_TABLE
linux-yocto-efi-test: Remove EFI_WARN_ON_ILLEGAL_ACCESSES patches
linux-yocto-efi-test: Bump kernel to v4.11
linux-yocto-efi-test: Bump linux-libc-headers to v4.11
linux-yocto-efi-test: Allocate pages without sleeping
linux-yocto-efi-test: remove __init attribute from memory mapping
functions
linux-yocto-efi-test: Save EFI_MEMORY_MAP passed by firmware
permanently
linux-yocto-efi-test: Copy support functions to install/uninstall
original_memory_map
linux-yocto-efi-test: Allow efi_mem_desc_lookup find illegally
accessed EFI regions
linux-yocto-efi-test: Add function to fixup page faults in illegal
efi regions
linux-yocto-efi-test: Fixup faults from UEFI firmware
linux-yocto-efi-test: Introduce EFI_WARN_ON_ILLEGAL_ACCESSES
linux-yocto-efi-test: Re-enable EFI_WARN_ON_ILLEGAL_ACCESSES
luv-test: Add support to dump dmesg, cpuinfo and ACPI tables
4 years, 3 months
[PATCH 0/2] Updates for CHIPSEC in LUV
by Ricardo Neri
Now that CHIPSEC v1.3.1 is out. It might be good to update LUV to use it.
These two patches deal with this.
While bumping to v1.3.1, one our patches to not include CHIPSEC
documentation needed a trivial update. Also, now CHIPSEC determines which
version of the Linux module it needs to build (32-bit or 64-bit) based on
the kernel running in the host machine. This makes cross-compiling
difficult. Thus, this change was reverted. Instead, we allow setup.py
determine the correct version.
Lastly, the CHIPSEC team has recommended to not run the tool with the -i
option as it may lead to spurious results. This is fixed.
Thanks and BR,
Ricardo
Ricardo Neri (2):
chipsec: run CHIPSEC without the -i option
chipsec: bump to v1.3.1
...issue-with-building-driver-on-32bit-syste.patch | 43 ++++++++++++++++++++++
.../chipsec/0001-chipsec-do-not-ship-manual.patch | 4 +-
meta-luv/recipes-core/chipsec/chipsec/chipsec | 2 +-
meta-luv/recipes-core/chipsec/chipsec_git.bb | 5 ++-
4 files changed, 49 insertions(+), 5 deletions(-)
create mode 100644 meta-luv/recipes-core/chipsec/chipsec/0001-Revert-fix-issue-with-building-driver-on-32bit-syste.patch
--
2.7.4
4 years, 3 months