Uploaded image for project: 'Linux Kernel Quality'
  1. Linux Kernel Quality
  2. LKQ-236

UEFI validation in kernelci

    XMLWordPrintable

    Details

    • Type: Epic
    • Status: Closed
    • Priority: Undecided
    • Resolution: Delivered
    • Affects Version/s: None
    • Fix Version/s: 2019.08
    • Component/s: None
    • Labels:
      None
    • Epic Name:
      UEFI validation in kernelci
    • Upstream:
      Yes

      Description

      Date: Tue, 12 Feb 2019 13:34:40 +0100
      From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
      To: Dan Rue <dan.rue@linaro.org>, Matt Hart <matthew.hart@linaro.org>, Graeme Gregory <graeme.gregory@linaro.org>, Leif Lindholm <leif.lindholm@linaro.org>,
      Mark Brown <broonie@linaro.org>
      Subject: UEFI validation in kernelci
      X-Date: Tue, 12 Feb 2019 06:34:40 -0600

      Hi,

      Given that I am serving as the Linux EFI subsystem maintainer, it is
      my job to ensure that the changes I merge get proper test coverage,
      and I recently found out that kernelci (plus Matty's lab) only gives
      me proper coverage for arm64, since the QEMU x86 VMs boot in legacy
      BIOS mode only. This resulted in some breakage in -next (which got
      reverted quickly), so going forward, I'd like to improve the coverage
      for the EFI and -next trees, and cover at least the following
      configurations:

      i386
      x86_64 w/32-bit UEFI (aka mixed mode)
      x86_64 w/64-bit UEFI
      arm64* w/GICv2+DT
      arm64* w/GICv3+DT
      arm64* w/GICv2+ACPI
      arm64* w/GICv3+ACPI
      ARM w/GICv2
      ARM w/GICv3

      (*RNG enabled for KASLR)

      all booting in graphical UEFI mode, not u-boot or legacy BIOS.

      Fortunately, all these cases can be covered with QEMU instances, but
      if I understand the kernelci team correctly, the way LAVA embeds QEMU
      today does not permit a -bios argument to be passed, and so whatever
      QEMU provides as a default is used (which is no firmware on arm and
      legacy SeaBIOS on x86)

      Since this does not involve actual hardware, I'm happy to host a lab
      myself (or as part of the LDCG infrastructure) that plugs into
      kernelci, but I do need help getting the prerequisite LAVA changes in
      place.

      So could we get this work planned and resourced in the foreseeable future?

      Thanks,
      Ard.

        Attachments

          Issue Links

            Structure

              People

              Assignee:
              anders.roxell@linaro.org Anders Roxell
              Reporter:
              dan.rue@linaro.org Dan Rue [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: