All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Hoffmann <kraxel@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: Zixuan Wang <zxwang42@gmail.com>,
	kvm@vger.kernel.org, pbonzini@redhat.com, marcorr@google.com,
	erdemaktas@google.com, rientjes@google.com, seanjc@google.com,
	brijesh.singh@amd.com, Thomas.Lendacky@amd.com,
	varad.gautam@suse.com, jroedel@suse.de, bp@suse.de
Subject: Re: [kvm-unit-tests PATCH v1 0/3] x86 UEFI: pass envs and args
Date: Tue, 22 Feb 2022 07:11:44 +0100	[thread overview]
Message-ID: <20220222061144.st3lrvkt3d6paqqx@sirius.home.kraxel.org> (raw)
In-Reply-To: <20220221152558.2fwtzrkoq53t66ie@gator>

  Hi,

> > EFI wrapper scripts for each unit test can be generated to pass the args
> > to the unit test EFI apps automatically. For the environment, the EFI
> > vars can be set as usual for the system. For QEMU, that means creating
> > a VARS.fd and then adding another flash device to the VM to exposes it.
> 
> BTW, this tool from Gerd might be useful for that
> 
> https://gitlab.com/kraxel/edk2-tests/-/blob/master/tools/vars.py

Probably not (yet) as this right now focuses on stuff needed for secure
boot, i.e. enroll certificates etc.

Setting variables with ascii (or unicode) strings should be rather easy
to add though.

take care,
  Gerd


      parent reply	other threads:[~2022-02-22  6:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-20 22:42 [kvm-unit-tests PATCH v1 0/3] x86 UEFI: pass envs and args Zixuan Wang
2022-02-20 22:42 ` [kvm-unit-tests PATCH v1 1/3] x86 UEFI: pull UEFI definitions for file operations Zixuan Wang
2022-02-20 22:42 ` [kvm-unit-tests PATCH v1 2/3] x86 UEFI: read envs from file Zixuan Wang
2022-02-20 22:42 ` [kvm-unit-tests PATCH v1 3/3] x86 UEFI: read args " Zixuan Wang
2022-02-21  8:40 ` [kvm-unit-tests PATCH v1 0/3] x86 UEFI: pass envs and args Andrew Jones
2022-02-21 15:25   ` Andrew Jones
2022-02-21 18:47     ` Zixuan Wang
2022-02-22  6:11     ` Gerd Hoffmann [this message]

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=20220222061144.st3lrvkt3d6paqqx@sirius.home.kraxel.org \
    --to=kraxel@redhat.com \
    --cc=Thomas.Lendacky@amd.com \
    --cc=bp@suse.de \
    --cc=brijesh.singh@amd.com \
    --cc=drjones@redhat.com \
    --cc=erdemaktas@google.com \
    --cc=jroedel@suse.de \
    --cc=kvm@vger.kernel.org \
    --cc=marcorr@google.com \
    --cc=pbonzini@redhat.com \
    --cc=rientjes@google.com \
    --cc=seanjc@google.com \
    --cc=varad.gautam@suse.com \
    --cc=zxwang42@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.