public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, gaoliming@byosoft.com.cn, rebecca@nuviainc.com
Cc: 'Leif Lindholm' <leif@nuviainc.com>,
	'Ard Biesheuvel' <ardb+tianocore@kernel.org>
Subject: Re: 回复: [edk2-devel] [PATCH 1/1] ArmPkg: Fix ARM ProcessorSubClassDxe build
Date: Wed, 17 Feb 2021 20:41:38 -0700	[thread overview]
Message-ID: <d4c4b7d9-15fc-e239-ba57-e08efecf42aa@bsdio.com> (raw)
In-Reply-To: <000d01d705a6$cf2075c0$6d616140$@byosoft.com.cn>

Liming,

It was found via Linaro's CI environment, but not EDK2's.
I'm planning to set up my own Jenkins server to run CI to catch problems 
like this before they're committed. It'll also let me test OvmfPkg/Bhyve 
builds too.

-- 
Rebecca Cran

On 2/17/21 8:33 PM, gaoliming wrote:
> Rebecca:
>    Is this issue detected in open CI environment?
> 
> Thanks
> Liming
>> -----邮件原件-----
>> 发件人: bounce+27952+71573+4905953+8761045@groups.io
>> <bounce+27952+71573+4905953+8761045@groups.io> 代表 Rebecca Cran
>> 发送时间: 2021年2月10日 23:05
>> 收件人: devel@edk2.groups.io
>> 抄送: Rebecca Cran <rebecca@nuviainc.com>; Leif Lindholm
>> <leif@nuviainc.com>; Ard Biesheuvel <ardb+tianocore@kernel.org>
>> 主题: [edk2-devel] [PATCH 1/1] ArmPkg: Fix ARM ProcessorSubClassDxe build
>>
>> The ARM ProcessorSubClassDxe build was broken due to changes in the
>> SmbiosProcessor API and an unused variable.
>>
>> Signed-off-by: Rebecca Cran <rebecca@nuviainc.com>
>> ---
>>   ArmPkg/Universal/Smbios/ProcessorSubClassDxe/SmbiosProcessorArm.c | 6
>> ++----
>>   1 file changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git
>> a/ArmPkg/Universal/Smbios/ProcessorSubClassDxe/SmbiosProcessorArm.c
>> b/ArmPkg/Universal/Smbios/ProcessorSubClassDxe/SmbiosProcessorArm.c
>> index 0be4403c765f..c78bd41a7e06 100644
>> ---
>> a/ArmPkg/Universal/Smbios/ProcessorSubClassDxe/SmbiosProcessorArm.c
>> +++
>> b/ArmPkg/Universal/Smbios/ProcessorSubClassDxe/SmbiosProcessorArm.c
>> @@ -22,7 +22,7 @@
>>       @return The cache size.
>>   **/
>>   UINT64
>> -ArmGetCacheSize (
>> +SmbiosProcessorGetCacheSize (
>>     IN UINT8   CacheLevel,
>>     IN BOOLEAN DataCache,
>>     IN BOOLEAN UnifiedCache
>> @@ -66,14 +66,13 @@ ArmGetCacheSize (
>>       @return The cache associativity.
>>   **/
>>   UINT32
>> -ArmGetCacheAssociativity (
>> +SmbiosProcessorGetCacheAssociativity (
>>     IN UINT8   CacheLevel,
>>     IN BOOLEAN DataCache,
>>     IN BOOLEAN UnifiedCache
>>     )
>>   {
>>     CCSIDR_DATA  Ccsidr;
>> -  CCSIDR2_DATA Ccsidr2;
>>     CSSELR_DATA  Csselr;
>>     BOOLEAN      CcidxSupported;
>>     UINT32       Associativity;
>> @@ -88,7 +87,6 @@ ArmGetCacheAssociativity (
>>     CcidxSupported = ArmHasCcidx ();
>>
>>     if (CcidxSupported) {
>> -    Ccsidr2.Data = ReadCCSIDR2 (Csselr.Data);
>>       Associativity = Ccsidr.BitsCcidxAA32.Associativity + 1;
>>     } else {
>>       Associativity = Ccsidr.BitsNonCcidx.Associativity + 1;
>> --
>> 2.26.2
>>
>>
>>
>>
>>
> 
> 
> 
> 
> 
> 
> 
> 



  reply	other threads:[~2021-02-18  3:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 15:04 [PATCH 1/1] ArmPkg: Fix ARM ProcessorSubClassDxe build Rebecca Cran
2021-02-10 20:17 ` Leif Lindholm
2021-02-18  3:33 ` 回复: [edk2-devel] " gaoliming
2021-02-18  3:41   ` Rebecca Cran [this message]
2021-02-18  5:54     ` Sami Mujawar

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=d4c4b7d9-15fc-e239-ba57-e08efecf42aa@bsdio.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