U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Simon Glass <sjg@chromium.org>
Cc: Masahisa Kojima <masahisa.kojima@linaro.org>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Alexander Graf <agraf@csgraf.de>, Bin Meng <bmeng.cn@gmail.com>,
	Christian Gmeiner <christian.gmeiner@gmail.com>
Subject: Re: [PATCH v3 1/3] efi_loader: add SMBIOS table measurement
Date: Fri, 1 Oct 2021 22:47:10 +0300	[thread overview]
Message-ID: <YVdlvpThuqr8jksL@apalos.home> (raw)
In-Reply-To: <CAPnjgZ2Dj26mXRyoGQdZDu9frW2OPTPOka2mNCf6hH0A=7Q5jw@mail.gmail.com>

Hi Simon, 

[...]
> As part of this work, can you or someone else at Linaro please add
> tests for the SMBIOS code?
> 
> Also as mentioned in the previous version, we should have tests for
> this. Ilias suggested what needs to be added to the sandbox emulator.

I pointed out what's missing on the sandbox.  Asking for the tests is
fine and those will be added,  but since the TPM is already working in
QEMU,  I strongly prefer doing it there.

I know you like sandbox and you are trying to promote using it for testing, 
but imho having it for the TPM is not the best of examples.  You are adding 
code emulating a really complex device.  There's *always* going to be
missing functionality (not to mention bugs). 

The EFI TCG tests will ask more and more from the TPM.  E.g there's a call for 
changing the active PCRs which we haven't implemented yet in EFI.  We'll have
to keep adding  complex features to sandbox for every patch?
QEMU and it's TPM already work and have all the functionality we'll ever need.
In fact this [1] came out from testing on QEMU.   So since QEMU and testing
is an acceptable way for testing U-Boot,  I'll resend my TPM MMIO patchset
and we can create the tests there.

[1] https://source.denx.de/u-boot/custodians/u-boot-efi/-/commit/346cee3ac5782fefeaeda2b54914b029547adf52


Thanks
/Ilias

  reply	other threads:[~2021-10-01 19:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-01 11:18 [PATCH v3 0/3] Enhance Measured Boot Masahisa Kojima
2021-10-01 11:18 ` [PATCH v3 1/3] efi_loader: add SMBIOS table measurement Masahisa Kojima
2021-10-01 15:23   ` Simon Glass
2021-10-01 19:47     ` Ilias Apalodimas [this message]
2021-10-21  0:12   ` Heinrich Schuchardt
2021-10-21  8:38     ` Masahisa Kojima
2021-10-21  8:49       ` Heinrich Schuchardt
2021-10-21 12:52         ` Masahisa Kojima
2021-10-21 12:59           ` Heinrich Schuchardt
2021-10-21 13:41             ` Masahisa Kojima
2021-11-02 14:56               ` Simon Glass
2021-11-04  1:26                 ` Masahisa Kojima
2021-10-01 11:18 ` [PATCH v3 2/3] efi_loader: add UEFI GPT measurement Masahisa Kojima
2021-10-01 15:23   ` Simon Glass
2021-10-22 10:49     ` Masahisa Kojima
2021-10-01 16:28   ` Heinrich Schuchardt
2021-10-04  3:11     ` Masahisa Kojima
2021-10-01 11:18 ` [PATCH v3 3/3] efi_loader: add DeployedMode and AuditMode variable measurement Masahisa Kojima
2021-10-01 16:43   ` Heinrich Schuchardt
2021-10-04  2:30     ` Masahisa Kojima
2021-10-22  8:04       ` Masahisa Kojima

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=YVdlvpThuqr8jksL@apalos.home \
    --to=ilias.apalodimas@linaro.org \
    --cc=agraf@csgraf.de \
    --cc=bmeng.cn@gmail.com \
    --cc=christian.gmeiner@gmail.com \
    --cc=masahisa.kojima@linaro.org \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox