public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Devel EDK2 <devel@edk2.groups.io>,
	"jordan.l.justen@intel.com" <jordan.l.justen@intel.com>,
	"lersek@redhat.com" <lersek@redhat.com>
Subject: Re: [PATCH v1] OvmfPkg: Use DxeRuntimeCapsuleLib from DxeCapsuleLibFmp in X64 builds
Date: Mon, 24 Jun 2019 12:24:08 +0100	[thread overview]
Message-ID: <72cb7134-d04c-cde6-e028-83e4cb94aa94@solarflare.com> (raw)
In-Reply-To: <CAKv+Gu8fr44mujsA_26AOUV7DV1q=mjN_2X9BjFUefmgDeoY6g@mail.gmail.com>



On 24/06/2019 12:15, Ard Biesheuvel wrote:
> On Mon, 24 Jun 2019 at 12:33, Tomas Pilar <tpilar@solarflare.com> wrote:
>> Switching to this library enables capsule support for FMP devices. Simple
>> tests show that a capsule with an embedded driver now updates using
>> CapsuleApp.
>>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Signed-off-by: Tomas Pilar <tpilar@solarflare.com>
> I don't have a problem with this change unless it affects the code
> size considerably.
>
> However, isn't this only useful for updating the firmware on PCI cards
> from within a VM when they are passed through from the host to the
> guest? I understand this is a useful test scenario for you, but at
> least clarify this in the commit log.
The library itself is tiny. The use case you describe is exactly what I am using at the moment.
I can imagine that software testing FMP implementation APIs is also something that might be
useful. I will clarify in the commit.
>
>> ---
>>  OvmfPkg/OvmfPkgX64.dsc | 2 +-
>>  1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/OvmfPkg/OvmfPkgX64.dsc b/OvmfPkg/OvmfPkgX64.dsc
>> index 39ac791565..4c41e59a75 100644
>> --- a/OvmfPkg/OvmfPkgX64.dsc
>> +++ b/OvmfPkg/OvmfPkgX64.dsc
>> @@ -125,7 +125,7 @@
>>    UefiBootManagerLib|MdeModulePkg/Library/UefiBootManagerLib/UefiBootManagerLib.inf
>>    BootLogoLib|MdeModulePkg/Library/BootLogoLib/BootLogoLib.inf
>>    FileExplorerLib|MdeModulePkg/Library/FileExplorerLib/FileExplorerLib.inf
>> -  CapsuleLib|MdeModulePkg/Library/DxeCapsuleLibNull/DxeCapsuleLibNull.inf
>> +  CapsuleLib|MdeModulePkg/Library/DxeCapsuleLibFmp/DxeRuntimeCapsuleLib.inf
>>    DxeServicesLib|MdePkg/Library/DxeServicesLib/DxeServicesLib.inf
>>    DxeServicesTableLib|MdePkg/Library/DxeServicesTableLib/DxeServicesTableLib.inf
>>    PeCoffGetEntryPointLib|MdePkg/Library/BasePeCoffGetEntryPointLib/BasePeCoffGetEntryPointLib.inf
>> --
>> 2.17.2
>>


      reply	other threads:[~2019-06-24 11:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b079ba367694437c9e8062eb347997a8@ukex01.SolarFlarecom.com>
2019-06-24 10:33 ` [PATCH v1] OvmfPkg: Use DxeRuntimeCapsuleLib from DxeCapsuleLibFmp in X64 builds Tomas Pilar (tpilar)
2019-06-24 11:15   ` Ard Biesheuvel
2019-06-24 11:24     ` Tomas Pilar (tpilar) [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-list 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=72cb7134-d04c-cde6-e028-83e4cb94aa94@solarflare.com \
    --to=devel@edk2.groups.io \
    /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