From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from NAM11-CO1-obe.outbound.protection.outlook.com (NAM11-CO1-obe.outbound.protection.outlook.com [40.107.220.74]) by mx.groups.io with SMTP id smtpd.web10.20143.1664948338057980790 for ; Tue, 04 Oct 2022 22:38:58 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@amd.com header.s=selector1 header.b=stGyF3xp; spf=permerror, err=parse error for token &{10 18 %{i}._ip.%{h}._ehlo.%{d}._spf.vali.email}: invalid domain name (domain: amd.com, ip: 40.107.220.74, mailfrom: abner.chang@amd.com) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=b08SOaMfsHRi2MZEoTP+/43fF+1E7kS2WkKszQ3KycILL8vWKi68qiGYEffSKR6UaeSA9TD/SnJ+oSkY/QK6bKT9w0isLG55zSKcfjWtrxZRl/6Fm5RSwMtNAPW/lq5hAOAjhhKPGP43TijwKHP6A4huGoZ5R7azOl+Cm5APzLtxDVeRRw1N9gBE/j3PxuLmqfdjAnw6BLrYRv2v1Dk5RvQIATT1CvNujoyX2RQt0u2LumylSgbUtODg/CjfHJU0UR6k+Y3V8oPB+HPRn8DFreMzyqnu0gAsRE5wH/FrAS/WyPCjc51TPnjXdwd1ZlLSjJvTtbQqCLoQadXSWubrqA== 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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=r7P/y4k0R1ZamBCLAox0UWBY4IAL8YMfYv63C0MFiZ4=; b=VQ9OI7aLaRNltlB8aWhZzUNldFqrEY6BCBu5SIa2Lb/61+smRxno6TpPhcFCVDWAdP2rJnt8IHpqdnBdBTpnv0tEi4/zsnvXGJI/m/v0apQz13xFNdsl09gvnPmotqEztDd2jrZD9mXTkqSRt+YqKfRHJ2RnWnh0yG7gA/nJQ8bRpiuSuqyyRmTDWtE2olB3s8IdvwgVLIdeqNmtXgRBee1ys+QAFdb4sr5IWpKczlOdm+tl1UOPx59FzBGGhDhYakp4/kgsCDQUO534bg0gW8BOKtaplshs+OII5Qf8HzRfFdEtDl/Qrk5ILWO0W0aL4RF/gYSfxQv6Q/Zh/gwAQg== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amd.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=r7P/y4k0R1ZamBCLAox0UWBY4IAL8YMfYv63C0MFiZ4=; b=stGyF3xpxFp66g7iH3RQJqg7Cw0Ut7hfg8JzpR+ViRam2xDZZ3CKoNUgRxUZiY3JAGzHqSl78IAuYA6adTPEZLU1pcByc6kmWHOtLouE3VMHvQRlGA2xl+tRNT/aBlIg5ifedg3qgZG30nYrmMrEpCPqX3F9z09R2WHNfOCVwbA= Received: from MN2PR12MB3966.namprd12.prod.outlook.com (2603:10b6:208:165::18) by SN7PR12MB7250.namprd12.prod.outlook.com (2603:10b6:806:2aa::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.5676.31; Wed, 5 Oct 2022 05:38:55 +0000 Received: from MN2PR12MB3966.namprd12.prod.outlook.com ([fe80::dd29:6efb:1027:cfb2]) by MN2PR12MB3966.namprd12.prod.outlook.com ([fe80::dd29:6efb:1027:cfb2%5]) with mapi id 15.20.5676.031; Wed, 5 Oct 2022 05:38:53 +0000 From: "Chang, Abner" To: "Kinney, Michael D" , "devel@edk2.groups.io" , "quic_llindhol@quicinc.com" , "Ni, Ray" , "Attar, AbdulLateef (Abdul Lateef)" , Sunil V L CC: lichao , "Kirkendall, Garrett" , "Grimes, Paul" , "He, Jiangang" , Andrew Fish Subject: Re: [edk2-devel] The principles of EDK2 module reconstruction for archs Thread-Topic: [edk2-devel] The principles of EDK2 module reconstruction for archs Thread-Index: AdjPX4ZZG0rDXS4WTdOIWvoiYOLYcgC9rttQAC2dmIAADxJbkAAiVmtwAABqVrAAMdRUkAARY7IwAAF/rYAABYT70AB0Z6+AAAYqDgAAADksgAAYA9igACxnOYAAAHOkMAAgQPVg Date: Wed, 5 Oct 2022 05:38:53 +0000 Message-ID: References: <0c1ee7b8-9ecf-3f46-ac36-9d1464831263@quicinc.com> In-Reply-To: Accept-Language: zh-CN, en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: msip_labels: MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Enabled=true; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_SetDate=2022-10-05T05:38:47Z; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Method=Standard; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_Name=General; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_SiteId=3dd8961f-e488-4e60-8e11-a82d994e183d; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_ActionId=a0d1594a-9ca9-4fcb-8b30-fa8cf4841f9a; MSIP_Label_4342314e-0df4-4b58-84bf-38bed6170a0f_ContentBits=1 authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com; x-ms-publictraffictype: Email x-ms-traffictypediagnostic: MN2PR12MB3966:EE_|SN7PR12MB7250:EE_ x-ms-office365-filtering-correlation-id: 95ce245d-a745-4511-e390-08daa693e37d x-ms-exchange-senderadcheck: 1 x-ms-exchange-antispam-relay: 0 x-microsoft-antispam: BCL:0; x-microsoft-antispam-message-info: +b7voJVb+aU9BRPUNA00XezptOKtOsdnBWNwPGTPoDLIty4ssuSTtvyMRlOh1BxLM8zqJEQrPWNeAlQ9u5hGpcToSWyl0ZKpgrHYCMSJKjMWTMfeayYSnqsVaeCCgQ5wn2yHb1iMM4uD8+n7XwauGOVItn2UchjUEFtKrYHIh9Hh4K4BqNR3ILU7NLc2GXZvcZovD5m8sfnFog5f2rsAf6Ew0W/n31I5mnTml/moN80dSZ+2MKRCvOcuc1tKqUCRInzMvZAht1Zto5b5rjDpQEVIV/76a3A9dZyw+SwenfdZ1S5ySCYbRuZXCczhMmQLKWauMtGCXzWs1GgOXpCtqdiY2/+Le+ncr2v44xa3qOi90717b8aMiTN6WrggrJhGY/3Y8f9sVmQTyStovdwWL9ae298aCjy+z59tgZOlmN5zM7EYrsWlGGLDNTG7n85OI+h3VqCDG7BYJIhLoz6pjVAOLqVnigRn89aCtOB/IbDf27C0l9D12xsf68oGZvVvE8x8kluxEsh4PYGRR+TsLQOhNI+Eb0Ap3DmMK6qoNBnfUKcqhpL0hPExoSWqLMtWf5OvBfR8t0F42Gssm51ERiELhnVyJwgw2xu2n6NRQYZ/+fufWqGzdUDOA6Mncd8VbsxqkzbFXcZbyihVrtr+cKTd377hZVNA65fa5T7SEpChYr9tZfeFgqvAOwcCq9abi3Yq4KArOL3BRf1GyvL+MY95tKZv80SafDd8FJgdoGG/PiaIJSHI3CKjt2Uu81sidvRJl42R59MKb78Z2+7WdzjvIesaO8cjK7q924f4TeyhpAAmJGOix/GNqgOVwdrqTBAYtbRNEVBPnSkAXZHDSg== x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MN2PR12MB3966.namprd12.prod.outlook.com;PTR:;CAT:NONE;SFS:(13230022)(4636009)(366004)(136003)(396003)(376002)(346002)(39860400002)(451199015)(45080400002)(71200400001)(66899015)(478600001)(9686003)(8936002)(316002)(19627235002)(33656002)(38070700005)(122000001)(5660300002)(38100700002)(186003)(66446008)(4326008)(66556008)(66946007)(66476007)(64756008)(8676002)(76116006)(6506007)(7696005)(2906002)(54906003)(110136005)(26005)(52536014)(55016003)(966005)(53546011)(30864003)(83380400001)(86362001)(41300700001)(559001)(579004);DIR:OUT;SFP:1101; x-ms-exchange-antispam-messagedata-chunkcount: 1 x-ms-exchange-antispam-messagedata-0: =?us-ascii?Q?+T1faJn7V68jpuNnPMmRW336HrsMeiEm7L/VkCeuY2B6z4FdSgWDcFVief35?= =?us-ascii?Q?DQZ9iN3tdq8e0qrDM/+0uQSOC9SDHh36XRWzBf7JDeAu9Fti8S149QkQzJBX?= =?us-ascii?Q?nRtt+mxbDyRmzdsbjMJMFGWTDfNvB6R9PTQww0p+e8/rpHMXvpAkSluhZg1Y?= =?us-ascii?Q?vGk1qW7UuDO5F8zbsXlmUmJmPYh0Xs+TUxY9pjnvGl8EQg0e4R60VXV501c8?= =?us-ascii?Q?Hdlw+Dfja5A51k7wpntNI/fPai3/zZyZQG/glhmU4HEpLbZCeo3hwsMl5tWz?= =?us-ascii?Q?61DrwycBwZgmr6ksrZYgQJxp/T1E748kEUj4U7QTXmMj1Rz7WTrGbTj7hy58?= =?us-ascii?Q?6Pl0ocLH2Q6XsPPExna58AnLsJAbWfsGhIh5eq4Ckx2iLU3eOKCZqJxca+jk?= =?us-ascii?Q?FVIg3FseYXibRXc5EnfSiLFhqaI3wIRtPytXi5WxEfJ/236ckn8U72nq7IEk?= =?us-ascii?Q?80uyGn8p3L23IyUSsUseUG92GnuA8NbdV7MRbwRu+WbrUhfX/wsIQO306wcm?= =?us-ascii?Q?RLXRpdMewuZb/hROkTxHQ6L8WdGYKMwYdG2lM9OKNG/R86kZWcpSuaw3K7WJ?= =?us-ascii?Q?uUGnXdbLcl1VOGzaMP40903Q6RY2rk2vsoU/W+HH+S+YAcnyQ4RKMW6rv+n6?= =?us-ascii?Q?uYqE7MjBL/biL6w2Czxxn7jolWP2JGdY201enUnWlwoQ/cS3OjlJPj4/i98a?= =?us-ascii?Q?oBMMLFPR1B6WQayXxDGIWPDtB6DpVKhJW1vZlZCHhm2rYiqja03mfKJhUAAl?= =?us-ascii?Q?3+uHJwx7C0siPgaskayjNamyHVMGjmOChnRJjqjrLkStgh0sOIKcL0HuOL9z?= =?us-ascii?Q?PnFksKfOS3aOV/kJGqUYiAsVgkuUn0uRx7XSuD8kgMiIjh0fDIx8chrbc5RV?= =?us-ascii?Q?W3T8b+SbVoCC4h58+doK1WFAFs5Lwvnm4Ypw6sjxpo2/MQQWCxMCNriLnJFm?= =?us-ascii?Q?rhGOBgG/tMKN04FBPP1aQ0bfnB5ihH7YfXqtfvpkiXKt2r2xTrw8QIZt2u2F?= =?us-ascii?Q?gBaSdggtZdFMiOoL8oD0MN0QwX8jJkFwbkGa00G+tdPDuSEU5ES5vV5s6Vnl?= =?us-ascii?Q?8br0mv/JvkttpeihpxhlEHKS1frsZrejs7FfZ2/U1kzz9Wx3FE/EqfWzLesb?= =?us-ascii?Q?MqG7qw7DaQAdUtJeYAQXXNxBFHm9ClPuqD475nClrr6wq5gqmxvOOmhbnNQo?= =?us-ascii?Q?FKWiJpO48vNXpoXtDJEs7/RfR3750WjQZWpo/zo1MgaJ0EmYsBAUGt+nyDD4?= =?us-ascii?Q?V35O6fWHDinLHHHFXuexMy4OE8qZvOoGbHAHcMrCMenKy/CI/WtJCWl19ruG?= =?us-ascii?Q?YkZzQ0TI5wYt/FojE6IzmYIA8b/PZAp4Lzoj4Ax46ExbneTyDY9LP83cE65a?= =?us-ascii?Q?xR2Ob1rrcPdARZgfuHU9xsuq+2brj1c747V1xoBj+wTAZZGttFWHxFZn33AC?= =?us-ascii?Q?4mumdXBx3Fl8aEg6lCd8HtA215do6WWkhwR+u/6L0fOJiZdoxPqphp//r7d3?= =?us-ascii?Q?1EW8/kzCJ8GSrr3N1k6ieeaMR998cn/TVyI1khIjVGG5w7TcdsZ0mH/VkH2N?= =?us-ascii?Q?hUykgd+tbkV+lVdIt24=3D?= MIME-Version: 1.0 X-OriginatorOrg: amd.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: MN2PR12MB3966.namprd12.prod.outlook.com X-MS-Exchange-CrossTenant-Network-Message-Id: 95ce245d-a745-4511-e390-08daa693e37d X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Oct 2022 05:38:53.3271 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 3dd8961f-e488-4e60-8e11-a82d994e183d X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-CrossTenant-userprincipalname: IdB1jSQmoepOAG24BbpitzEMJSd1not2PKsGQR+Engb3kyPws3/uSdDlxxR/08rESXsaQrV4Ak79gcNMFcoCrw== X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN7PR12MB7250 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable [AMD Official Use Only - General] PR updated https://github.com/tianocore-docs/edk2-CCodingStandardsSpecification/pull/2= /commits. Please check it. Thanks Abner > -----Original Message----- > From: Kinney, Michael D > Sent: Tuesday, October 4, 2022 10:18 PM > To: Chang, Abner ; devel@edk2.groups.io; > quic_llindhol@quicinc.com; Ni, Ray ; Attar, AbdulLateef > (Abdul Lateef) ; Sunil V L > ; Kinney, Michael D > Cc: lichao ; Kirkendall, Garrett > ; Grimes, Paul ; He, > Jiangang ; Andrew Fish > Subject: RE: [edk2-devel] The principles of EDK2 module reconstruction fo= r archs >=20 > Caution: This message originated from an External Source. Use proper caut= ion > when opening attachments, clicking links, or responding. >=20 >=20 > I would not add link to Wiki from EDK II C Coding Standard Specification. >=20 > We want documents published from tianocore-docs to support standalone > formats such as PDF and if there is a link in one of those documents, we = want to > know that it is a permanent link. I am concerned we may reorganize Wiki = pages > and links in PDF would become stale. >=20 > Links from Wiki to specs makes sense. >=20 > Mike >=20 > > -----Original Message----- > > From: Chang, Abner > > Sent: Tuesday, October 4, 2022 7:05 AM > > To: Kinney, Michael D ; > > devel@edk2.groups.io; quic_llindhol@quicinc.com; Ni, Ray > > ; Attar, AbdulLateef (Abdul Lateef) > > ; Sunil V L > > Cc: lichao ; Kirkendall, Garrett > > ; Grimes, Paul ; He, > > Jiangang ; Andrew Fish > > Subject: RE: [edk2-devel] The principles of EDK2 module reconstruction > > for archs > > > > [AMD Official Use Only - General] > > > > > > > > > -----Original Message----- > > > From: Kinney, Michael D > > > Sent: Tuesday, October 4, 2022 12:54 AM > > > To: devel@edk2.groups.io; Chang, Abner ; > > > quic_llindhol@quicinc.com; Ni, Ray ; Attar, > > > AbdulLateef (Abdul Lateef) ; Sunil V L > > > ; Kinney, Michael D > > > > > > Cc: lichao ; Kirkendall, Garrett > > > ; Grimes, Paul ; > > > He, Jiangang ; Andrew Fish > > > Subject: RE: [edk2-devel] The principles of EDK2 module > > > reconstruction for archs > > > > > > Caution: This message originated from an External Source. Use proper > > > caution when opening attachments, clicking links, or responding. > > > > > > > > > Hi Abner, > > > > > > responses below. > > > > > > Mike > > > > > > > -----Original Message----- > > > > From: devel@edk2.groups.io On Behalf Of > > > > Chang, Abner via groups.io > > > > Sent: Sunday, October 2, 2022 10:37 PM > > > > To: Kinney, Michael D ; > > > > devel@edk2.groups.io; quic_llindhol@quicinc.com; Ni, Ray > > > > ; Attar, AbdulLateef (Abdul Lateef) > > > > ; Sunil V L > > > > Cc: lichao ; Kirkendall, Garrett > > > > ; Grimes, Paul ; > > > He, > > > > Jiangang ; Andrew Fish > > > > Subject: Re: [edk2-devel] The principles of EDK2 module > > > > reconstruction for archs > > > > > > > > [AMD Official Use Only - General] > > > > > > > > Mike, > > > > Agree. This can be mentioned on the Wiki page. Also, this would > > > > require the discussion between maintainer and contributor. I would > > > > say > > > maintainer has the responsibility to make sure an arch folder is > > > only created when necessary. > > > > > > Agreed > > Ok, I will update Directory and file names section. > > > > > > > > > > > Do you agree with the arch concatenate solution for arch folder? > > > > That > > > means IA32_X64 instead of X86 (I am fine with this)? > > > > > > Yes > > > > > > > However, there is one scenario. Assume there were two arch folders > > > > IA32_X64 and RISCV64. Then ARM shares the code with IA32_X64, we > > > > may > > > rename IA32_X64 to IA32_X64_ARM. > > > > Although the directory naming is not real a problem to the build, > > > > a separate ARM folder seems easier? Or we can just allow this kind > > > > of folder > > > naming structure, however we let maintainer to make the decision? > > > > > > I would let the maintainer make the decision. For your example, > > > another approach may be to move the IA32_X64 content up a level so > > > it is common and is used by IA32, X64, ARM. And leave RISCV64 > > > folder for an arch that has special requirements. I think having > > > some flexibility in the guidelines is very beneficial. The main > > > goal is for consistency when a specific guideline is followed. > > I think we can have the naming rules in the edk2 C coding standard spec= and > put these guidelines on the Wiki page. > > Is that ok to have a link to Wiki page in the edk2 C coding standard sp= ec? > > > > Abner > > > > > > > > > > > > > Abner > > > > > > > > > > > > > -----Original Message----- > > > > > From: Kinney, Michael D > > > > > Sent: Monday, October 3, 2022 1:18 PM > > > > > To: Chang, Abner ; devel@edk2.groups.io; > > > > > quic_llindhol@quicinc.com; Ni, Ray ; Attar, > > > > > AbdulLateef (Abdul Lateef) ; Sunil V > > > > > L ; Kinney, Michael D > > > > > > > > > > Cc: lichao ; Kirkendall, Garrett > > > > > ; Grimes, Paul > > > > > ; He, Jiangang ; > > > > > Andrew Fish > > > > > Subject: RE: [edk2-devel] The principles of EDK2 module > > > > > reconstruction for archs > > > > > > > > > > Caution: This message originated from an External Source. Use > > > > > proper caution when opening attachments, clicking links, or respo= nding. > > > > > > > > > > > > > > > Abner, > > > > > > > > > > I think another guideline is to minimize the number of subdirecto= ries. > > > > > > > > > > Only create them if it helps with the organization and long term > > > > > maintenance of the component. > > > > > > > > > > Mike > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > From: Chang, Abner > > > > > > Sent: Sunday, October 2, 2022 8:13 PM > > > > > > To: Kinney, Michael D ; > > > > > > devel@edk2.groups.io; quic_llindhol@quicinc.com; Ni, Ray > > > > > > ; Attar, AbdulLateef (Abdul Lateef) > > > > > > ; Sunil V L > > > > > > > > > > > > Cc: lichao ; Kirkendall, Garrett > > > > > > ; Grimes, Paul > > > ; > > > > > He, > > > > > > Jiangang ; Andrew Fish > > > > > > Subject: RE: [edk2-devel] The principles of EDK2 module > > > > > > reconstruction for archs > > > > > > > > > > > > [AMD Official Use Only - General] > > > > > > > > > > > > Hi Mike and Leif, > > > > > > First of all, we don't use arch folder if the module is mainly > > > > > > for a specific arch in obviously. So we will have both common > > > > > > and arch-specific > > > > > files constructed under module/library root. > > > > > > > > > > > > > > https://nam11.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fe= d > > > > > k > > > > > 2 > > > > > > > > > > .groups.io%2Fg%2Fdevel%2Fmessage%2F94567&data=3D05%7C01%7CA > > > > > bner.Chan > > > > > > > > > > > > > > > g%40amd.com%7Cd49cbbe6d3d942bd69a308daa4fea41b%7C3dd8961fe4884 > > > > > e608e11a > > > > > > > > > > > > > > > 82d994e183d%7C0%7C0%7C638003710850252776%7CUnknown%7CTWFpbGZ > > > > > sb3d8eyJWI > > > > > > > > > > > > > > > joiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3 > > > > > 000%7 > > > > > > > > > > > > > > C%7C%7C&sdata=3DeiLOC0G9WZWKqm2ALcAiKr7SPBP5AgDdAxogHlv5pI > > > > > M%3D&r > > > > > > eserved=3D0 > > > > > > SmmCpuFeatureLib\Ia32 > > > > > > SmmCpuFeatureLib\X64 > > > > > > SmmCpuFeatureLib\SmmCpuFeatureLib.c > > > > > > SmmCpuFeatureLib\SmmCpuFeatureLibCommon.c > > > > > > SmmCpuFeatureLib\IntelSmmCPuFeaturesLib > > > > > > SmmCpuFeatureLib\AmdlSmmCPuFeaturesLib > > > > > > > > > > > > > > > > > > > > Could we concatenate architectures? > > > > > > > > I.e. AARCH64_ARM, IA32_X64, AARCH64_RISCV64... ? > > > > > > Looks like below? > > > > > > > > > > > > CpuDxe\IA32_X64\IA32\abc.nasm > > > > > > CpuDxe\IA32_X64\X64\abc.nasm > > > > > > CpuDxe\IA32_X64\CpuDxe.c > > > > > > CpuDxe\IA32_X64\AmdCpuDxe.c > > > > > > CpuDxe\IA32_X64\IntelCpuDxe.c > > > > > > CpuDxe\RiscV64\CpuDxe.c > > > > > > CpuDxe\ARM\CpuDxe.c > > > > > > CpuDxe\ > > > > > > CpuDxeCommon.c // If required. > > > > > > CpuDxe.inf // Use INF section arc= h modifier for X86, > > > RISC-V > > > > > and ARM. > > > > > > CpuDxeAmd.inf // Separate INF for AMD. > > > > > > > > > > > > Seems ok, but is AARCH64_RISCV64 a real case? Or it means we > > > > > > can create a folder "AARCH64_RISCV64" when there are some > > > > > > common > > > files > > > > > shared by AARCH64 and RISCV64? > > > > > > > > > > > > For the 32/64 bit support, it can still stay under module root > > > > > > and don't need to assign a folder for them unless the arch has > > > > > > the different > > > > > implementation. > > > > > > Regards, > > > > > > Abner > > > > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > From: Kinney, Michael D > > > > > > > Sent: Saturday, October 1, 2022 2:52 AM > > > > > > > To: devel@edk2.groups.io; quic_llindhol@quicinc.com; Chang, > > > > > > > Abner ; Ni, Ray ; > > > > > > > Attar, AbdulLateef (Abdul Lateef) > > > > > > > ; Sunil V L > > > > > > > ; Kinney, Michael D > > > > > > > > > > > > > > Cc: lichao ; Kirkendall, Garrett > > > > > > > ; Grimes, Paul > > > > > > > ; He, Jiangang ; > > > > > > > Andrew Fish > > > > > > > Subject: RE: [edk2-devel] The principles of EDK2 module > > > > > > > reconstruction for archs > > > > > > > > > > > > > > Caution: This message originated from an External Source. > > > > > > > Use proper caution when opening attachments, clicking links, > > > > > > > or > > > responding. > > > > > > > > > > > > > > > > > > > > > Hi Leif, > > > > > > > > > > > > > > Concatenation is a good idea. Makes it more obvious and can > > > > > > > be easily adopted for new CPU archs. > > > > > > > > > > > > > > There is an additional case where an implementation does not > > > > > > > have differences based on CPU Arch or Vendor, but it does > > > > > > > have differences based on the bit- width of the CPU. Take > > > > > > > BaseSafeIntLib as > > > > > an example. > > > > > > > It has source files for 32-bit CPUs, 64-bit CPUs, and CPU > > > > > > > arch specific file for Ebc because Ebc adapts to 32-bit or > > > > > > > 64-bit depending on the CPU type the EBC Interpreter is runni= ng. > > > > > > > > > > > > > > MdePkg/Library/BaseSafeIntLib/ > > > > > > > BaseSafeIntLib.inf > > > > > > > SafeIntLib.c > > > > > > > SafeIntLib32.c > > > > > > > SafeIntLib64.c > > > > > > > SafeIntLibEbc.c > > > > > > > > > > > > > > Should we add "32" and "64" as supported suffices in file nam= es? > > > > > > > > > > > > > > If we wanted to put type content into a subdirectory, what > > > > > > > would be the suggested directory name for "32" and "64". Or > > > > > > > do we want to require this type of difference to always be > > > > > > > files in top level directory of > > > > > the modules/library? > > > > > > > > > > > > > > Best regards, > > > > > > > > > > > > > > Mike > > > > > > > > > > > > > > > > > > > > > > -----Original Message----- > > > > > > > > From: devel@edk2.groups.io On > > > > > > > > Behalf Of Leif Lindholm > > > > > > > > Sent: Friday, September 30, 2022 9:09 AM > > > > > > > > To: devel@edk2.groups.io; Kinney, Michael D > > > > > > > > ; Chang, Abner > > > > > ; > > > > > > > > Ni, Ray ; Attar, AbdulLateef (Abdul > > > > > > > > Lateef) ; Sunil V L > > > > > > > > > > > > > > > > Cc: lichao ; Kirkendall, Garrett > > > > > > > > ; Grimes, Paul > > > > > ; > > > > > > > > He, Jiangang ; Andrew Fish > > > > > > > > > > > > > Subject: Re: [edk2-devel] The principles of EDK2 module > > > > > > > > reconstruction for archs > > > > > > > > > > > > > > > > I agree similar things will certainly happen for > > > > > > > > ARM/AARCH64, which will probably be noticeable when I > > > > > > > > start eradicating ArmPkg and putting the arch-standard bits= into > (mostly) MdePkg. > > > > > > > > > > > > > > > > But I like the ability to see already at the filesystem > > > > > > > > level which files belong to the architecture I'm currently > > > > > > > > working on and > > > > > which don't. > > > > > > > > > > > > > > > > Could we concatenate architectures? > > > > > > > > I.e. AARCH64_ARM, IA32_X64, AARCH64_RISCV64... ? > > > > > > > > > > > > > > > > / > > > > > > > > Leif > > > > > > > > > > > > > > > > On 2022-09-30 08:28, Michael D Kinney wrote: > > > > > > > > > Hi Abner, > > > > > > > > > > > > > > > > > > One comment is on adding a new CPU type dir name of 'X86' > > > > > > > > > for content that is common for IA32/X64. > > > > > > > > > > > > > > > > > > I can imagine a similar case for ARM/AARCH64 and for the > > > > > > > > > RISCV (32, 64, 128) cases. > > > > > > > > > > > > > > > > > > I think I would prefer to drop X86 and if there are > > > > > > > > > files that are common to multiple CPU architectures then > > > > > > > > > they are considered common and are in top directory of > > > > > > > > > module and the file header and INF file can clearly > > > > > > > > > document which CPU archs the file > > > > > applies. > > > > > > > > > > > > > > > > > > Mike > > > > > > > > > > > > > > > > > >> -----Original Message----- > > > > > > > > >> From: Chang, Abner > > > > > > > > >> Sent: Friday, September 30, 2022 12:11 AM > > > > > > > > >> To: Ni, Ray ; Attar, AbdulLateef > > > > > > > > >> (Abdul > > > > > > > > >> Lateef) ; Sunil V L > > > > > > > > >> ; devel@edk2.groups.io; > > > > > > > > >> Kinney, Michael D > > > > > > > > >> Cc: lichao ; Kirkendall, Garrett > > > > > > > > >> ; Grimes, Paul > > > > > > > > >> ; He, Jiangang > > > ; > > > > > Leif > > > > > > > > >> Lindholm ; Andrew Fish > > > > > > > > >> > > > > > > > > >> Subject: RE: [edk2-devel] The principles of EDK2 module > > > > > > > > >> reconstruction for archs > > > > > > > > >> > > > > > > > > >> [AMD Official Use Only - General] > > > > > > > > >> > > > > > > > > >> Thanks Ray, here are my responses. > > > > > > > > >> https://nam11.safelinks.protection.outlook.com/?url=3Dht= t > > > > > > > > >> ps%3 > > > > > > > > >> A%2F > > > > > > > > >> %2Fg > > > > > > > > >> ithub.com%2Ftianocore-docs%2Fedk2- > > > > > CCodingStandardsSpecification > > > > > > > > >> %2Fp > > > > > > > > >> > > > > > > > > > > > > > > > > ull%2F2&data=3D05%7C01%7CAbner.Chang%40amd.com%7C7c3292c8bd2 > > > > > f4 > > > > > > > 86f > > > > > > > > >> > > > > > > > > > > > > > > > > 920908daa314e8e6%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C6 > > > > > > > 3800 > > > > > > > > >> > > > > > > > > > > > > > > > > 1607445876768%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC > > > > > JQ > > > > > > > IjoiV > > > > > > > > >> > > > > > > > > > > > > > > > > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > > > > > =3D > > > > > > > HAq > > > > > > > > >> > > > > > > > > ou4JyY1yxDthuQ1dEKcF7Q3o4W77Oo9rOOvkXNWU%3D&reserved=3D0 > > > > > > > > >> > > > > > > > > >> @Kinney, Michael D we may also need your clarification > > > > > > > > >> on the > > > > > comments. > > > > > > > > >> > > > > > > > > >> > > > > > > > > >>> -----Original Message----- > > > > > > > > >>> From: Ni, Ray > > > > > > > > >>> Sent: Thursday, September 29, 2022 3:42 PM > > > > > > > > >>> To: Attar, AbdulLateef (Abdul Lateef) > > > > > > > > >>> ; Chang, Abner > > > > > > > > >>> ; Sunil V L > > > > > > > > >>> ; devel@edk2.groups.io > > > > > > > > >>> Cc: Kinney, Michael D ; > > > > > > > > >>> lichao ; Kirkendall, Garrett > > > > > > > > >>> ; Grimes, Paul > > > > > > > > >>> ; He, Jiangang > > > ; > > > > > > > > >>> Leif Lindholm ; Andrew Fish > > > > > > > > >>> > > > > > > > > >>> Subject: RE: [edk2-devel] The principles of EDK2 > > > > > > > > >>> module reconstruction for archs > > > > > > > > >>> > > > > > > > > >>> Caution: This message originated from an External Sourc= e. > > > > > > > > >>> Use proper caution when opening attachments, clicking > > > > > > > > >>> links, or > > > > > responding. > > > > > > > > >>> > > > > > > > > >>> > > > > > > > > >>> Abner, > > > > > > > > >>> Comments in > > > > > > > > >>> https://nam11.safelinks.protection.outlook.com/?url=3Dh= t > > > > > > > > >>> tps% > > > > > > > > >>> 3A%2 > > > > > > > > >>> F%2F > > > > > > > > >>> gith > > > > > > > > >>> ub.com%2Ftianocore-docs%2Fedk2- > > > > > > > > >>> CCodingStandardsSpecification%2Fpull%2F2%23pullrequest > > > > > > > > >>> revi > > > > > > > > >>> ew- > > > > > > > > >>> > > > > > > > > > > > > > > > > 1124763311&data=3D05%7C01%7CAbner.Chang%40amd.com%7Cd825e24 > > > > > > > > >>> > > > > > > > > > > > > > > > > 8625541e3f43e08daa1ee2883%7C3dd8961fe4884e608e11a82d994e183d%7C0 > > > > > > > > >>> > > > > > > > > > > > > > > > > %7C0%7C638000341502885565%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC > > > > > > > > >>> > > > > > > > > > > > > > > > > 4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000% > > > > > > > > >>> > > > > > > > > > > > > > > > 7C%7C%7C&sdata=3DRXxgpbEr6ivbqP1R6%2B3Rxl%2ByJAnaUJuaYYKdfCH > > > > > > > > >>> 8jo8%3D&reserved=3D0 > > > > > > > > >>> > > > > > > > > >>> We can discuss more in tomorrow's meeting. > > > > > > > > >>> > > > > > > > > >>> > > > > > > > > >>>> -----Original Message----- > > > > > > > > >>>> From: Attar, AbdulLateef (Abdul Lateef) > > > > > > > > >>>> > > > > > > > > >>>> Sent: Thursday, September 29, 2022 3:11 PM > > > > > > > > >>>> To: Chang, Abner ; Sunil V L > > > > > > > > >>>> ; devel@edk2.groups.io; Ni, > > > > > > > > >>>> Ray > > > > > > > > >>>> Cc: Kinney, Michael D ; > > > > > > > > >>>> lichao ; Kirkendall, Garrett > > > > > > > > >>>> ; Grimes, Paul > > > > > > > > >>>> ; > > > > > > > > >>> He, > > > > > > > > >>>> Jiangang ; Leif Lindholm > > > > > > > > >>>> ; Andrew Fish > > > > > > > > >>>> > > > > > > > > >>>> Subject: RE: [edk2-devel] The principles of EDK2 > > > > > > > > >>>> module reconstruction for archs > > > > > > > > >>>> > > > > > > > > >>>> Hi Abner, > > > > > > > > >>>> Looks good to me. > > > > > > > > >>>> Reviewed-by: Abdul Lateef Attar > > > > > > > > >>>> > > > > > > > > >>>> Thanks > > > > > > > > >>>> AbduL > > > > > > > > >>>> > > > > > > > > >>>> -----Original Message----- > > > > > > > > >>>> From: Chang, Abner > > > > > > > > >>>> Sent: 28 September 2022 20:31 > > > > > > > > >>>> To: Sunil V L ; > > > > > > > > >>>> devel@edk2.groups.io; ray.ni@intel.com > > > > > > > > >>>> Cc: Kinney, Michael D ; > > > > > > > > >>>> lichao ; Kirkendall, Garrett > > > > > > > > >>>> ; Grimes, Paul > > > > > > > > >>>> ; > > > > > > > > >>> He, > > > > > > > > >>>> Jiangang ; Attar, AbdulLateef > > > > > > > > >>>> (Abdul > > > > > > > > >>>> Lateef) ; Leif Lindholm > > > > > > > > >>>> ; Andrew Fish > > > > > > > > >>>> > > > > > > > > >>>> Subject: RE: [edk2-devel] The principles of EDK2 > > > > > > > > >>>> module reconstruction for archs > > > > > > > > >>>> > > > > > > > > >>>> [AMD Official Use Only - General] > > > > > > > > >>>> > > > > > > > > >>>> I just had created PR to update edkII C coding > > > > > > > > >>>> standard spec for the file and directory naming. We > > > > > > > > >>>> can review and confirm this update first and then go > > > > > > > > >>>> back to the principles of EDK2 module > > > > > > > reconstruction for archs. > > > > > > > > >>>> Here is the PR: > > > > > > > > >>>> > > > > > > > > >>> https://nam11.safelinks.protection.outlook.com/?url=3Dh= t > > > > > > > > >>> tps% > > > > > > > > >>> 3A%2 > > > > > > > > >>> F%2F > > > > > > > > >>> gith > > > > > > > > >>>> ub.com%2Ftianocore-docs%2Fedk2- > > > > > > > > >>> &data=3D05%7C01%7CAbner.Chang%40amd.c > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > om%7Cd825e248625541e3f43e08daa1ee2883%7C3dd8961fe4884e608e11a82 > > > > > > > > >>> d994e18 > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > 3d%7C0%7C0%7C638000341502885565%7CUnknown%7CTWFpbGZsb3d8eyJ > > > > > > > > >>> WIjoiMC4wLj > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C% > > > > > > > > >>> 7C%7C&a > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > mp;sdata=3DX4z9puj81nIGTqtMxC9igDZyBPOT6OTWSU%2BjoIowo%2BE%3D&a > > > > > > > > >>> mp;reserv > > > > > > > > >>>> ed=3D0 > > > > > > > > >>>> CCodingStandardsSpecification/pull/2 > > > > > > > > >>>> > > > > > > > > >>>> The naming rule is mainly for the new module or new fi= le IMO. > > > > > > > > >>>> Some existing module may not meet the guidelines > > > > > > > > >>>> mentioned in this > > > > > > > spec. > > > > > > > > >>>> Thus we need the principles of EDK2 module > > > > > > > > >>>> reconstruction on the existing module to support > > > > > > > > >>>> other processor archs and not impacting the > > > > > > > > >>> existing platforms (e.g. > > > > > > > > >>>> rename the INF file or directory to meet the guideline= s). > > > > > > > > >>>> > > > > > > > > >>>> Sunil, seems RISC-V CpuDxe meet the guideline. Please > > > > > > > > >>>> check > > > it. > > > > > > > > >>>> Just feel that having CpuDxe.c to Riscv64 folder is > > > > > > > > >>>> not quite a best solution. I think at least we can > > > > > > > > >>>> abstract the protocol structure and protocol > > > > > > > > >>>> installation under CpuDxe\ and have the arch > > > > > > > > >>>> implementation under arch folder. We can discuss this > > > > > > > > >>>> later after we confirming the > > > > > > > > >>> guideline and principles. > > > > > > > > >>>> > > > > > > > > >>>> Thanks > > > > > > > > >>>> Abner > > > > > > > > >>>> > > > > > > > > >>>>> -----Original Message----- > > > > > > > > >>>>> From: Sunil V L > > > > > > > > >>>>> Sent: Wednesday, September 28, 2022 3:34 PM > > > > > > > > >>>>> To: devel@edk2.groups.io; ray.ni@intel.com > > > > > > > > >>>>> Cc: Chang, Abner ; Kinney, > > > Michael > > > > > > > > >>>>> D ; lichao > > > > > > > > >>>>> ; Kirkendall, Garrett > > > > > > > > >>>>> ; Grimes, Paul > > > > > > > > >>>>> ; He, Jiangang > > > > > > > > >>>>> ; Attar, AbdulLateef (Abdul > > > > > > > > >>>>> Lateef) ; Leif Lindholm > > > > > > > > >>>>> ; Andrew Fish > > > > > > > > >>>>> > > > > > > > > >>>>> Subject: Re: [edk2-devel] The principles of EDK2 > > > > > > > > >>>>> module reconstruction for archs > > > > > > > > >>>>> > > > > > > > > >>>>> Caution: This message originated from an External Sou= rce. > > > > > > > > >>>>> Use proper caution when opening attachments, > > > > > > > > >>>>> clicking links, or > > > > > responding. > > > > > > > > >>>>> > > > > > > > > >>>>> > > > > > > > > >>>>> On Wed, Sep 28, 2022 at 03:33:45AM +0000, Ni, Ray wro= te: > > > > > > > > >>>>> Hi Ray, > > > > > > > > >>>>>> > > > > > > > > >>>>>> 1. When a new arch's implementation is > > > > > > > > >>>>>> introduced to the existing > > > > > > > > >>>>> module which was developed for the specific arch: > > > > > > > > >>>>>> > > > > > > > > >>>>>> 1. The folder reconstruction: > > > > > > > > >>>>>> > > > > > > > > >>>>>> * Create arch folder for the existing arch impl= ementation > > > > > > > > >>>>>> [Ray] Do you move existing arch implementation to > > > > > > > > >>>>>> that arch > > > > > folder? > > > > > > > > >>>>>> It will > > > > > > > > >>>>> break existing platforms a lot. > > > > > > > > >>>>>> > > > > > > > > >>>>>> * Create the arch folder for the new introduced= arch > > > > > > > > >>>>>> [Ray] I agree. But if we don't create arch folder > > > > > > > > >>>>>> for existing arch > > > > > > > > >>>>> implementation, the pkg layout will be a mess. > > > > > > > > >>>>>> > > > > > > > > >>>>>> [Ray] Hard for me to understand all the principles h= ere. > > > > > > > > >>>>>> Maybe we review > > > > > > > > >>>>> existing code including to-be-upstreamed code and > > > > > > > > >>>>> decide how > > > > > to go. > > > > > > > > >>>>>> > > > > > > > > >>>>> > > > > > > > > >>>>> Could you please take a look below changes which is > > > > > > > > >>>>> trying to add RISC-V support for CpuDxe? > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> https://nam11.safelinks.protection.outlook.com/?url=3Dh= t > > > > > > > > >>> tps% > > > > > > > > >>> 3A%2 > > > > > > > > >>> F%2F > > > > > > > > >>> gith > > > > > > > > >>>>> ub.com%2Ftianocore%2Fedk2- > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > staging%2Fcommit%2Fbba1a11be47dd091734e185afbed73ea75708749& > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > data=3D05%7C01%7Cabner.chang%40amd.com%7Ca419e6a010d34fde464b08d > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > aa123e080%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C63799947 > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > 2732494527%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sd > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > ata=3DVq6pJLnn8yJrJhFZn7LfLbZzrtpG4n1VLWgAil6J38U%3D&reserved=3D0 > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> https://nam11.safelinks.protection.outlook.com/?url=3Dh= t > > > > > > > > >>> tps% > > > > > > > > >>> 3A%2 > > > > > > > > >>> F%2F > > > > > > > > >>> gith > > > > > > > > >>>>> ub.com%2Ftianocore%2Fedk2- > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > staging%2Fcommit%2F7fccf92a97a6d0618a20f10622220e78b3687906&da > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > ta=3D05%7C01%7Cabner.chang%40amd.com%7Ca419e6a010d34fde464b08daa1 > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > 23e080%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C63799947273 > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > 2494527%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > > 2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata > > > > > > > > >>>>> > > > > > > > > >>>> > > > > > > > > >>> > > > > > > > > > > > > > > > =3DxFmvUv58vh4AUAM17Qy9G5jZWFZlK2Ozt3njpG1e8%2BY%3D&reserv > > > > > > > > >>>>> ed=3D0 > > > > > > > > >>>>> > > > > > > > > >>>>> What do you suggest with above example? > > > > > > > > >>>>> > > > > > > > > >>>>> 1) Common INF for all architectures - but modify INF > > > > > > > > >>>>> alone, no > > > > > > > > >>>>> X86 folder creation. > > > > > > > > >>>>> > > > > > > > > >>>>> This is what I have done in the commit above. May be > > > > > > > > >>>>> of least impact to existing code since it is only INF= change. > > > > > > > > >>>>> But like you mentioned this is bit weird that X86 > > > > > > > > >>>>> files will remain in root folder directly along with > > > > > > > > >>>>> some common > > > files. > > > > > > > > >>>>> > > > > > > > > >>>>> 2) Common INF (CpuDxe.inf) + create arch folders > > > > > > > > >>>>> X86, X64, IA32, > > > > > > > > >>>>> RiscV64 etc > > > > > > > > >>>>> > > > > > > > > >>>>> IMO, this is probably the best approach. What would > > > > > > > > >>>>> be the challenges with this? > > > > > > > > >>>>> > > > > > > > > >>>>> 3) Separate INF for arch like CpuDxe.inf for x86, > > > > > > > > >>>>> CpuDxeRiscV64.inf for > > > > > > > > >>>> RISC-V. > > > > > > > > >>>>> > > > > > > > > >>>>> This again probably is not a good idea. > > > > > > > > >>>>> > > > > > > > > >>>>> 4) If the module/library is specific to one arch (ex: > > > > > > > > >>>>> SMM(X86), SBI(RISC-V)), then create separate INF. > > > > > > > > >>>>> > > > > > > > > >>>>> Thanks! > > > > > > > > >>>>> Sunil > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >=20 > > > >