public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Guo Dong" <guo.dong@intel.com>
To: Pierre Gondois <Pierre.Gondois@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>,
	"Ma, Maurice" <maurice.ma@intel.com>,
	"You, Benjamin" <benjamin.you@intel.com>, nd <nd@arm.com>
Subject: Re: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc
Date: Sun, 21 Jun 2020 02:14:00 +0000	[thread overview]
Message-ID: <BYAPR11MB36536A2480BDDC31064A03E69E960@BYAPR11MB3653.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DB7PR08MB3113AA027412D72F29AA8B568B980@DB7PR08MB3113.eurprd08.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 3937 bytes --]


Hi Pierre,

There is no trouble to update FDF file to increase FV size.  I will create a patch to support NOOPT build.

Thanks,
Guo

From: Pierre Gondois <Pierre.Gondois@arm.com>
Sent: Friday, June 19, 2020 2:55 AM
To: devel@edk2.groups.io; Dong, Guo <guo.dong@intel.com>; Ma, Maurice <maurice.ma@intel.com>; You, Benjamin <benjamin.you@intel.com>; nd <nd@arm.com>
Subject: RE: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc

Hello Guo,
Thank you for your quick answer. I am asking on a testing perspective, I am not using a pure IA32 UEFI payload image.
However, would it be possible to increase the FV size for the NOOPT build type, or not to advertise it in the DSC file? I believe the build configuration should work if advertised.
Again, this is only for testing purpose. I can also remove this configuration from my test suite if this is too much trouble.

Regards,
Pierre

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of Guo Dong via groups.io
Sent: 18 June 2020 23:17
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>; Pierre Gondois <Pierre.Gondois@arm.com<mailto:Pierre.Gondois@arm.com>>; Ma, Maurice <maurice.ma@intel.com<mailto:maurice.ma@intel.com>>; You, Benjamin <benjamin.you@intel.com<mailto:benjamin.you@intel.com>>; nd <nd@arm.com<mailto:nd@arm.com>>
Subject: Re: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc


Thanks Pierre to report this build failure.
The failure is caused by FV size increase when using build parameter "-b NOOPT".
Given this build option would almost double the build size and it is  seldom used, I prefer you update the FDF file to increase the FV size to solve it locally.

BTW, from your build command, you are trying to build a pure IA32 UEFI payload image,  are you still using pure IA32 UEFI payload?
I ask this question because I plan to add pure X64 UEFI payload support and drop pure IA32 UEFI payload if possible.
Of course UEFI payload will continue support IA32 entrypoint and switch to X64 before DXE core.

Thanks,
Guo

From: devel@edk2.groups.io<mailto:devel@edk2.groups.io> <devel@edk2.groups.io<mailto:devel@edk2.groups.io>> On Behalf Of PierreGondois
Sent: Thursday, June 18, 2020 7:55 AM
To: Ma, Maurice <maurice.ma@intel.com<mailto:maurice.ma@intel.com>>; Dong, Guo <guo.dong@intel.com<mailto:guo.dong@intel.com>>; You, Benjamin <benjamin.you@intel.com<mailto:benjamin.you@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>; nd <nd@arm.com<mailto:nd@arm.com>>
Subject: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc

Hello,
I am not actively using this platform, but I wanted to report an error when building one of the DSC files in the UefiPayloadPkg with the following configuration:
build -b NOOPT -a IA32 -t VS2017 -p edk2 edk2\UefiPayloadPkg\UefiPayloadPkgIa32.dsc

The following error occurs:
Generating PEIFV FV
#### ['GenFv', '-a', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\Ffs\\PEIFV.inf', '-o', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.Fv', '-i', Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.inf']
Return Value = 2
GenFv: ERROR 3000: Invalid
the required fv image size 0x406c8 exceeds the set fv image size 0x30000

Regards,
Pierre
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

[-- Attachment #2: Type: text/html, Size: 10607 bytes --]

  reply	other threads:[~2020-06-21  2:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-18 14:55 Build error for UefiPayloadPkgIa32.dsc PierreGondois
2020-06-18 22:16 ` Guo Dong
2020-06-19  9:55   ` [edk2-devel] " PierreGondois
2020-06-21  2:14     ` Guo Dong [this message]
2020-07-08 15:24       ` PierreGondois
2020-07-08 17:55         ` Guo Dong

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=BYAPR11MB36536A2480BDDC31064A03E69E960@BYAPR11MB3653.namprd11.prod.outlook.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