From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from EUR04-HE1-obe.outbound.protection.outlook.com (EUR04-HE1-obe.outbound.protection.outlook.com [40.107.7.72]) by mx.groups.io with SMTP id smtpd.web10.3308.1592560518776532979 for ; Fri, 19 Jun 2020 02:55:20 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@armh.onmicrosoft.com header.s=selector2-armh-onmicrosoft-com header.b=oHgTL9to; spf=pass (domain: arm.com, ip: 40.107.7.72, mailfrom: pierre.gondois@arm.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tbRA82GBwwZlIOYOSDKq7cUFRTMkpas52249M+XbwUQ=; b=oHgTL9tojSIMGIj/EUZLIHiiAnhTozkvlkc/hkRoXh36uBHUciqhuFhg8vtFSe2PZlA+bB0cTePmekaDQIe+W6rPQ2VgHM/VA5lXOhkE2stE5D2LzA8q9W69KqAViVxtMBr9xNYoA9Kwy3vniWPOE73byH9lIN2MYwJxLjLoYzM= Received: from DB6PR0802CA0037.eurprd08.prod.outlook.com (2603:10a6:4:a3::23) by DB7PR08MB3497.eurprd08.prod.outlook.com (2603:10a6:10:48::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22; Fri, 19 Jun 2020 09:55:15 +0000 Received: from DB5EUR03FT025.eop-EUR03.prod.protection.outlook.com (2603:10a6:4:a3:cafe::a3) by DB6PR0802CA0037.outlook.office365.com (2603:10a6:4:a3::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22 via Frontend Transport; Fri, 19 Jun 2020 09:55:15 +0000 X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; edk2.groups.io; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;edk2.groups.io; dmarc=bestguesspass action=none header.from=arm.com; Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com; Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT025.mail.protection.outlook.com (10.152.20.104) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.22 via Frontend Transport; Fri, 19 Jun 2020 09:55:15 +0000 Received: ("Tessian outbound 866352848bb9:v59"); Fri, 19 Jun 2020 09:55:15 +0000 X-CR-MTA-TID: 64aa7808 Received: from 3ca059ad8c25.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 22588E12-A57B-4408-92B4-A046424FCF19.1; Fri, 19 Jun 2020 09:55:10 +0000 Received: from EUR05-AM6-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 3ca059ad8c25.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Fri, 19 Jun 2020 09:55:10 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=YST+MLgzo3y70vh4prrWH8v8w9fT24DCIal6PIMNL971mBWfqC8YPXQnO4Ziu79NM0bCp42OqBG98R+esoUOfh1IOEz8rvLvG3J997lK91Uab/NlTtuHUXcyzvIC4aarjw29WYkGjb8mAVfHySc/ucUkXjUXBf57Q2rAer0BlWfINpoQ6CZyVx/6hKfDilUFwxG0FwCVemL7GP4VCEGDnSh/TZNrTcXUkY4zOoO+OKY+Pnj32wXdxphmV1Y2XlwIw+xsHz1yUlBIDYn7v1QyNb0Hrc1WxL1wC1867nuKHlCMQ00FC1+OrRmDiXkHk7rbbAglopUIBdpShxkwLdlSGA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tbRA82GBwwZlIOYOSDKq7cUFRTMkpas52249M+XbwUQ=; b=EKM8GVhT5JrB5clSzLvrH1QA++5CN6oZ92D2dnzBhcq0jYbt0g1fsAyBB882hgP4dfzDCQAMN3o8PBGs2dzsnr5CHY5lL8+V5ybebdE2DRMLdJ3qIS/Fx9eLBNTtkayv8lZXRqyn9onEw8AMGzx2wXQfnUgzlqABbRv6pYKAO/j46HCVCq4dq9lQAnP8IGAnLrIM6bnJzX+PUY9q23DJA13dAwSRAXo0ZLpKCmRnWUjzM50zTiwQf5mq1PmKN9Ob+jtZLanz70OI43+PQib4ZGVe0I8ExBfo5zfLTa+UMxHzh0DJaNb8RLzcYZLXXhl5Zoyzin/PrN47JLjSkGGdOA== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com; s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=tbRA82GBwwZlIOYOSDKq7cUFRTMkpas52249M+XbwUQ=; b=oHgTL9tojSIMGIj/EUZLIHiiAnhTozkvlkc/hkRoXh36uBHUciqhuFhg8vtFSe2PZlA+bB0cTePmekaDQIe+W6rPQ2VgHM/VA5lXOhkE2stE5D2LzA8q9W69KqAViVxtMBr9xNYoA9Kwy3vniWPOE73byH9lIN2MYwJxLjLoYzM= Received: from DB7PR08MB3113.eurprd08.prod.outlook.com (2603:10a6:5:20::21) by DB7PR08MB3226.eurprd08.prod.outlook.com (2603:10a6:5:22::26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3109.23; Fri, 19 Jun 2020 09:55:07 +0000 Received: from DB7PR08MB3113.eurprd08.prod.outlook.com ([fe80::4178:71bd:a2a4:78bf]) by DB7PR08MB3113.eurprd08.prod.outlook.com ([fe80::4178:71bd:a2a4:78bf%7]) with mapi id 15.20.3109.021; Fri, 19 Jun 2020 09:55:07 +0000 From: "PierreGondois" To: "devel@edk2.groups.io" , "guo.dong@intel.com" , "Ma, Maurice" , "You, Benjamin" , nd Subject: Re: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc Thread-Topic: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc Thread-Index: AdZFgBMsodLFn79lQLy7ENmvIb5E9QAOzizgABimKkA= Date: Fri, 19 Jun 2020 09:55:07 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ts-tracking-id: 4d077ec1-76ad-440f-bfec-d5e07dbe7cea.0 x-checkrecipientchecked: true Authentication-Results-Original: edk2.groups.io; dkim=none (message not signed) header.d=none;edk2.groups.io; dmarc=none action=none header.from=arm.com; x-originating-ip: [217.140.106.52] x-ms-publictraffictype: Email X-MS-Office365-Filtering-HT: Tenant X-MS-Office365-Filtering-Correlation-Id: 3ff32498-40ff-4b57-b797-08d81436dda9 x-ms-traffictypediagnostic: DB7PR08MB3226:|DB7PR08MB3497: X-Microsoft-Antispam-PRVS: x-checkrecipientrouted: true nodisclaimer: true x-ms-oob-tlc-oobclassifiers: OLM:8882;OLM:8882; x-forefront-prvs: 0439571D1D X-MS-Exchange-SenderADCheck: 1 X-Microsoft-Antispam-Untrusted: BCL:0; X-Microsoft-Antispam-Message-Info-Original: Zy0pm+fDjuUYI+b0ukWjr4RSpvGovXg44TabwL/VlIK/Os8OBGARE0iVvD9AUvMTzy8s0JSNN2z15ibcm0dMBNd+CNgiukO/JgdgPMtSCv+4bP9ZVmNzSV/CrWGyrNiWBmt/qi8AQihheOYQLg3tXBw6bGl+uh8wj3bbdyMP6U0IGC9ylwNOVQCz5e9etCN84oKUHx4JksgXIJsS4kv4dmaUKBFGUiOV7zy+yzlyUE8lfNUIJBKOgiAazy+xQRA79AoC8JH4I0oNIgxuQwYC7yY9za9JhWf1hHekv2L4AHFlMBSDA2iGUuH65Q0ycmwjfYyWexc0U7FOkCkPXTGkxuqD3uMuxm9ZFZWvbIRTI06i0rgYb+XZNz5m7/aPIhar/EWZTdWdBSfcFWx42NevrQ== X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DB7PR08MB3113.eurprd08.prod.outlook.com;PTR:;CAT:NONE;SFTY:;SFS:(4636009)(39860400002)(366004)(376002)(346002)(136003)(396003)(33656002)(5660300002)(86362001)(166002)(52536014)(71200400001)(7696005)(8936002)(55016002)(186003)(6636002)(83380400001)(478600001)(26005)(110136005)(9326002)(9686003)(76236003)(316002)(2906002)(66476007)(66446008)(66946007)(76116006)(53546011)(6506007)(66556008)(8676002)(64756008);DIR:OUT;SFP:1101; x-ms-exchange-antispam-messagedata: I92ieryyPY4HW24OwKzyQVRon/CvRZkjnoJEtYeLyh6b6QbePwEv324VuFLuhpX2B3qCgNnVE6kzGe8ILBC05fMKB6xufRIMUjM+c1U3GMjSf7+kN1vt6RevNlTW2Yi90ng+AwO4Jg5DguTk78EF+qE49tY65noMAmoIB4aKgI5ZiejR40uIQlyijv+u3FDSLcXLz1rQnJa/2uWO5lFkZhYJBVYoBpbpa7JgFtGugCwa8lgPUsJNBtZtTu2iQUXkgGCPh0FI0lH3OxMIJtZoDw4tFR/r3OE6I2X6wdAcUgQbHImcRWJqiwsKjwt5+oexOccYwyOEW9CCUazILmTZOvzbJXBkZjPJRc9GolaX11gSnfoDPn05pVmvXgCCz3TijC0UlDH4ZRvzeHDtWnHbZT2dqmHyFQpeV08SrMtn/+ZGMVvoLXJUWGwPRZQIW3LcwlQM50OWaDPWSy/kqpdSyo4AtM9XoHCDtXuN0A/aLAUWogb30y7/GjSy2cqeowkk x-ms-exchange-transport-forked: True MIME-Version: 1.0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR08MB3226 Original-Authentication-Results: edk2.groups.io; dkim=none (message not signed) header.d=none;edk2.groups.io; dmarc=none action=none header.from=arm.com; Return-Path: Pierre.Gondois@arm.com X-EOPAttributedMessage: 0 X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT025.eop-EUR03.prod.protection.outlook.com X-Forefront-Antispam-Report: CIP:63.35.35.123;CTRY:IE;LANG:en;SCL:1;SRV:;IPV:CAL;SFV:NSPM;H:64aa7808-outbound-1.mta.getcheckrecipient.com;PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com;CAT:NONE;SFTY:;SFS:(4636009)(39860400002)(396003)(346002)(376002)(136003)(46966005)(82740400003)(86362001)(336012)(9686003)(7696005)(19627235002)(55016002)(478600001)(53546011)(5660300002)(8676002)(81166007)(9326002)(33656002)(47076004)(2906002)(8936002)(186003)(70586007)(316002)(70206006)(26005)(110136005)(6636002)(76236003)(166002)(83380400001)(356005)(82310400002)(6506007)(52536014);DIR:OUT;SFP:1101; X-MS-Office365-Filtering-Correlation-Id-Prvs: bc9d33f5-21c4-4293-91d8-08d81436d8e7 X-Forefront-PRVS: 0439571D1D X-Microsoft-Antispam: BCL:0; X-Microsoft-Antispam-Message-Info: fSanK/1r4zjp6W1G1Qsyh4ieFMAWKrl4H00aHv4WOxEYmpimTUDKyc4hrrh2IzUWs8fRG4UqxqITpAzwj8SvV/S3RMn1eDuepc49HR97DnJybg3cxPC9j71qLdYD5qqu5Csw3P3hRzGkLWoIJuBZW8v4S0M26vwvPfmbGHMmy+YkfeRmbLPEaeR4zOtvj6fM353YjnjMXxjRGp6pUqzlToD2f9DKupRs6ii4deqSBzbPOo2DxEiFiBLwnAj+S0cLIwKZumflpv2ojQb3KHxW7BM5agvudA4SLp0nYrLT4BKImnqXB13ZFs0Jyhncv8COb1IoUgtKfZENUrFZaiBPWIRYQ1MDKKzhU/HPKDHeqZctXeIKRmeGgSeoRPAvwgUIiAfswXpu8auGuSNOvzIM85U+ULJMFSItTXM/yrGweIaaTjFyv0cESGZVto/1lYWMDzfyOiqdA71ZbIpYQKhXpCqASqvFC01aN8uA73fye3Y= X-OriginatorOrg: arm.com X-MS-Exchange-CrossTenant-OriginalArrivalTime: 19 Jun 2020 09:55:15.2522 (UTC) X-MS-Exchange-CrossTenant-Network-Message-Id: 3ff32498-40ff-4b57-b797-08d81436dda9 X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d;Ip=[63.35.35.123];Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com] X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR08MB3497 Content-Language: en-US Content-Type: multipart/alternative; boundary="_000_DB7PR08MB3113AA027412D72F29AA8B568B980DB7PR08MB3113eurp_" --_000_DB7PR08MB3113AA027412D72F29AA8B568B980DB7PR08MB3113eurp_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello Guo, Thank you for your quick answer. I am asking on a testing perspective, I a= m 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 configura= tion should work if advertised. Again, this is only for testing purpose. I can also remove this configurat= ion from my test suite if this is too much trouble. Regards, Pierre From: devel@edk2.groups.io On Behalf Of Guo Dong vi= a groups.io Sent: 18 June 2020 23:17 To: devel@edk2.groups.io; Pierre Gondois ; Ma, Mau= rice ; You, Benjamin ; nd 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 N= OOPT". Given this build option would almost double the build size and it is seld= om 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 pay= load image, are you still using pure IA32 UEFI payload? I ask this question because I plan to add pure X64 UEFI payload support an= d 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 > On Behalf Of PierreGondois Sent: Thursday, June 18, 2020 7:55 AM To: Ma, Maurice >; Dong,= Guo >; You, Benjamin >; devel@edk2.groups.io; nd > Subject: [edk2-devel] Build error for UefiPayloadPkgIa32.dsc Hello, I am not actively using this platform, but I wanted to report an error whe= n building one of the DSC files in the UefiPayloadPkg with the following co= nfiguration: build -b NOOPT -a IA32 -t VS2017 -p edk2 edk2\UefiPayloadPkg\UefiPayloadPk= gIa32.dsc The following error occurs: Generating PEIFV FV #### ['GenFv', '-a', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\Ffs\\PE= IFV.inf', '-o', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.Fv', '-= i', Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEIFV.inf'] Return Value =3D 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 confi= dential and may also be privileged. If you are not the intended recipient, = please notify the sender immediately and do not disclose the contents to an= y 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 confi= dential and may also be privileged. If you are not the intended recipient, = please notify the sender immediately and do not disclose the contents to an= y other person, use it for any purpose, or store or copy the information in= any medium. Thank you. --_000_DB7PR08MB3113AA027412D72F29AA8B568B980DB7PR08MB3113eurp_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

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 bui= ld type, or not to advertise it in the DSC file? I believe the build config= uration should work if advertised.

Again, this is only for testing purpose. I can also remove this configu= ration from my test suite if this is too much trouble.

 

Regards,

Pierre

 

From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Guo Dong via groups.io
Sent: 18 June 2020 23:17
To: devel@edk2.groups.io; Pierre Gondois <Pierre.Gondois@arm.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

 

 

Thanks Pierre to report this build failure.

The failure is caused by FV size increase when using build parameter &#= 8220;-b NOOPT”.

Given this build option would almost double the build size and it is&nb= sp; seldom used, I prefer you update the FDF file to increase the FV size t= o 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 <devel= @edk2.groups.io> On Behalf Of PierreGondois
Sent: Thursday, June 18, 2020 7:55 AM
To: Ma, Maurice <maurice= .ma@intel.com>; Dong, Guo <= guo.dong@intel.com>; You, Benjamin <benjamin.you@intel.com>; devel@edk2.groups.io; nd <<= a href=3D"mailto:nd@arm.com">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 UefiPayloadPk= g with the following configuration:

build -b NOOPT -a IA32 -t VS2017 -p edk2 edk2\UefiP= ayloadPkg\UefiPayloadPkgIa32.dsc

 

The following error occurs:

Generating PEIFV FV

#### ['GenFv', '-a', 'Build\\UefiPayloadPkgIA32\\NO= OPT_VS2017\\FV\\Ffs\\PEIFV.inf', '-o', 'Build\\UefiPayloadPkgIA32\\NOOPT_VS= 2017\\FV\\PEIFV.Fv', '-i', Build\\UefiPayloadPkgIA32\\NOOPT_VS2017\\FV\\PEI= FV.inf']

Return Value =3D 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 an= y attachments are confidential and may also be privileged. If you are not t= he intended recipient, please notify the sender immediately and do not disc= lose the contents to any other person, use it for any purpose, or store or copy the information in any medium. T= hank you.

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