From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from loongson.cn (loongson.cn [114.242.206.163]) by mx.groups.io with SMTP id smtpd.web08.19174.1650531172687650731 for ; Thu, 21 Apr 2022 01:52:54 -0700 Authentication-Results: mx.groups.io; dkim=missing; spf=pass (domain: loongson.cn, ip: 114.242.206.163, mailfrom: lichao@loongson.cn) Received: from lichao-PC (unknown [10.40.24.65]) by mail.loongson.cn (Coremail) with SMTP id AQAAf9DxfxNdG2FiOhArAA--.54847S2; Thu, 21 Apr 2022 16:52:45 +0800 (CST) Date: Thu, 21 Apr 2022 16:52:45 +0800 From: "Chao Li" To: =?utf-8?Q?=22gaoliming=22?= Cc: "=?utf-8?Q?devel=40edk2.groups.io?=" , "=?utf-8?Q?spbrogan=40outlook.com?=" Message-ID: <3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com> In-Reply-To: <015801d85446$ae0d22d0$0a276870$@byosoft.com.cn> References: <015801d85446$ae0d22d0$0a276870$@byosoft.com.cn> Subject: =?UTF-8?B?UmU6IOWbnuWkjTogZWRrMi1kZXZlbF0gU29tZSBxdWVzdGlvbnMgYWJvdXQgQXp1cmUgQ0k=?= X-Mailer: Mailspring MIME-Version: 1.0 X-CM-TRANSID: AQAAf9DxfxNdG2FiOhArAA--.54847S2 X-Coremail-Antispam: 1UD129KBjvJXoW7WrWxJw47Zw4xGryfuFy8Krg_yoW8Wr43p3 sxua43Wr1kZw1UurW8Ja42g34Y9rn5XFW8Jr4kuw18K3sxCa42vr12vr4FgayDuryrtw1j vr1qvw4rXF1DKrJanT9S1TB71UUUUUUqnTZGkaVYY2UrUUUUjbIjqfuFe4nvWSU5nxnvy2 9KBjDU0xBIdaVrnRJUUUQKb7Iv0xC_Zr1lb4IE77IF4wAFF20E14v26r1j6r4UM7CY07I2 0VC2zVCF04k26cxKx2IYs7xG6rWj6s0DM7CIcVAFz4kK6r1j6r18M28lY4IEw2IIxxk0rw A2F7IY1VAKz4vEj48ve4kI8wA2z4x0Y4vE2Ix0cI8IcVAFwI0_Xr0_Ar1l84ACjcxK6xII jxv20xvEc7CjxVAFwI0_Gr1j6F4UJwA2z4x0Y4vEx4A2jsIE14v26F4UJVW0owA2z4x0Y4 vEx4A2jsIEc7CjxVAFwI0_GcCE3s1le2I262IYc4CY6c8Ij28IcVAaY2xG8wAqx4xG67k0 8I80eVWUJVW8JwAqx4xG62kEwI0EY4vaYxAvb48xMc02F40EFcxC0VAKzVAqx4xG6I80ew Aqx4xG64kEw2xG04xIwI0_Gr0_Xr1l5I8CrVC2j2CEjI02ccxYII8I67AEr4CY67k08wAv 7VC0I7IYx2IY67AKxVWUJVWUGwAv7VC2z280aVAFwI0_Jr0_Gr1lOx8S6xCaFVCjc4AY6r 1j6r4UM4x0Y48IcxkI7VAKI48JMx8GjcxK6IxK0xIIj40E5I8CrwCY02Avz4vE-syl42xK 82IYc2Ij64vIr41l4I8I3I0E4IkC6x0Yz7v_Jr0_Gr1lx2IqxVAqx4xG67AKxVWUGVWUWw C20s026x8GjcxK67AKxVWUGVWUWwC2zVAF1VAY17CE14v26r1Y6r17MIIYrxkI7VAKI48J MIIF0xvE2Ix0cI8IcVAFwI0_Jr0_JF4lIxAIcVC0I7IYx2IY6xkF7I0E14v26r1j6r4UMI IF0xvE42xK8VAvwI8IcIk0rVWrZr1j6s0DMIIF0xvEx4A2jsIE14v26r1j6r4UMIIF0xvE x4A2jsIEc7CjxVAFwI0_Jr0_GrUvcSsGvfC2KfnxnUUI43ZEXa7IU022NtUUUUU== X-CM-SenderInfo: xolfxt3r6o00pqjv00gofq/1tbiAQADCF3QvPPZyQADsb Content-Type: multipart/alternative; boundary="62611b5d_789b3192_440b" --62611b5d_789b3192_440b Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi Liming, For Q2, all ECC errors is come from register naming. I think what you are p= ointing out is not UEFI SPEC, we have the LoongArch ISA manual on GitHub wh= ere all of register naming are defined. Dose that means it is a public SPEC= ? If yes, what should I do to get the Azure CI ECC to pass? LoongArch ISA manual link: https://loongson.github.io/LoongArch-Documentati= on/LoongArch-Vol1-EN.html (https://link.getmailspring.com/link/3631883D-61F= 4-43B6-BFBD-B37C74C065F3@getmailspring.com/0?redirect=3Dhttps%3A%2F%2Floong= son.github.io%2FLoongArch-Documentation%2FLoongArch-Vol1-EN.html&recipient= =3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D) Hope you reply, thank you! -- Thanks, Chao ------------------------ On 4=E6=9C=88 20 2022, at 7:39 =E6=97=A9=E4=B8=8A, "gaoliming" wrote: > For Q2, if key word is defined in public spec, they can be handled as the= exception. You can see MdePkg\MdePkg.ci.yaml EccCheck section that has Exc= eptionList and IgnoreFiles. > > > Thanks > Liming > =E5=8F=91=E4=BB=B6=E4=BA=BA: devel@edk2.groups.io = =E4=BB=A3=E8=A1=A8 Sean > =E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8820=E6=97=A5 = 0:39 > =E6=94=B6=E4=BB=B6=E4=BA=BA: Chao Li ; devel@edk2.gro= ups.io > =E4=B8=BB=E9=A2=98: Re: [edk2-devel] Some questions about Azure CI > > > > > > Q1 - There should be more details in the actual log file, but your code h= as formatting errors. In the last few months, the uncrusitfy tool has been = introduced to get common formatting errors fixed. See details here: EDK II = Code Formatting =C2=B7 tianocore/tianocore.github.io Wiki (https://link.get= mailspring.com/link/3631883D-61F4-43B6-BFBD-B37C74C065F3@getmailspring.com/= 1?redirect=3Dhttps%3A%2F%2Fgithub.com%2Ftianocore%2Ftianocore.github.io%2Fw= iki%2FEDK-II-Code-Formatting&recipient=3DZGV2ZWxAZWRrMi5ncm91cHMuaW8%3D) > Q2 - New code additions require passing ECC. You will just need to work t= hrough the reported errors. > Thanks > Sean > > >=20 --62611b5d_789b3192_440b Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi Liming,

For Q2, all ECC errors is come from register = naming. I think what you are pointing out is not UEFI SPEC, we have the Loo= ngArch ISA manual on GitHub where all of register naming are defined. Dose = that means it is a public SPEC? If yes, what should I do to get the Azure C= I ECC to pass?


H= ope you reply, thank you!

--
Thanks,
Chao
---------------= ---------


On 4=E6=9C=88 20 2022, at 7:39 =E6=97=A9=E4=B8=8A, "gaoliming" &= lt;gaoliming@byosoft.com.cn> wrote:
For Q2, if key word is defined in pu= blic spec, they can be handled as the exception.  You can see MdePkg\M= dePkg.ci.yaml EccCheck section that has ExceptionList and IgnoreFiles.

 
=
Thanks

Liming

=E5=8F=91=E4=BB=B6=E4=BA=BA:<= /strong> devel@edk2.groups.io <devel@edk2.groups.io> <= /font>=E4=BB=A3=E8=A1=A8 Sean
=E5=8F=91=E9=80=81=E6=97=B6=E9=97=B4: 2022=E5=B9=B44=E6=9C=8820=E6=97=A5 0:39
=E6=94=B6=E4=BB=B6=E4=BA=BA: Chao Li <lichao@loongson.cn>; devel@edk2.groups.io<= /font>
=E4=B8=BB=E9=A2=98:&n= bsp;Re: [edk2-devel] Some questions about Azure CI
 

Q1 - There should be more details in the actual log file, but your= code has formatting errors.   In the last few months, the uncrus= itfy tool has been introduced to get common formatting errors fixed.  =  See details here: EDK I= I Code Formatting =C2=B7 tianocore/tianocore.github.io Wiki

Q2 - New code additions require passing ECC.  You will just need to= work through the reported errors. 

Thanks
Sea= n

3D"Sent --62611b5d_789b3192_440b--