public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: devel@edk2.groups.io, huangming@linux.alibaba.com
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>, guoheyi@linux.alibaba.com
Subject: Re: [edk2-devel] [PATCH edk2 v2 1/1] ArmPkg/ArmGic: Fix GICR_IPRIORITYR address wrong issue
Date: Wed, 24 Feb 2021 11:49:40 +0000	[thread overview]
Message-ID: <20210224114940.GL1664@vanye> (raw)
In-Reply-To: <cc12861a-24dd-7f9d-53a0-ac200806d97d@linux.alibaba.com>

Hi Ming,

Thanks for this.
However, just after I sent my reply, Heyi suggested another
improvement to this patch. Can you please implement that, and submit a
v2?

Best Regards,

Leif

On Wed, Feb 24, 2021 at 16:26:33 +0800, Ming Huang wrote:
> 
> 
> On 2/23/21 8:58 PM, Leif Lindholm wrote:
> > On Tue, Feb 23, 2021 at 13:42:49 +0100, Ard Biesheuvel wrote:
> >> On Tue, 23 Feb 2021 at 12:07, Ming Huang <huangming@linux.alibaba.com> wrote:
> >>>
> >>> The register address of GICR_IPRIORITYR is in SGI_base frame. Add
> >>> IPRIORITY_ADDRESS macro for getting GICR_IPRIORITYR address. Otherwise
> >>> GIC RAS error(Uncorrected software error) may report in ArmGicDxe.
> >>
> >> NOTE: missing sign-off
> >>
> >> Patch seems fine to me
> >>
> >> Tested-by: Ard Biesheuvel <ardb@kernel.org> # QEMU/kvm guest on ThunderX2
> > 
> > Also looks good in QEMU.
> > Reviewed-by: Leif Lindholm <leif@nuviainc.com>
> > 
> > Ming, can you confirm that the contribution conforms to the developer
> > certificate of origin by replyint with your Signed-off-by: ?
> 
> Sorry, I miss the Signed-off-by.
> please help to add my Signed-off-by:
> Signed-off-by: Ming Huang <huangming@linux.alibaba.com>
> 
> Thanks,
> Ming
> 
> > 
> >>
> >>
> >>
> >>> ---
> >>>  ArmPkg/Drivers/ArmGic/ArmGicLib.c | 5 ++++-
> >>>  1 file changed, 4 insertions(+), 1 deletion(-)
> >>>
> >>> diff --git a/ArmPkg/Drivers/ArmGic/ArmGicLib.c b/ArmPkg/Drivers/ArmGic/ArmGicLib.c
> >>> index 8ef32b33a1..b4d3965acb 100644
> >>> --- a/ArmPkg/Drivers/ArmGic/ArmGicLib.c
> >>> +++ b/ArmPkg/Drivers/ArmGic/ArmGicLib.c
> >>> @@ -30,6 +30,9 @@
> >>>  #define ICENABLER_ADDRESS(base,offset) ((base) + \
> >>>            ARM_GICR_CTLR_FRAME_SIZE +  ARM_GICR_ICENABLER + (4 * offset))
> >>>
> >>> +#define IPRIORITY_ADDRESS(base,offset) ((base) + \
> >>> +          ARM_GICR_CTLR_FRAME_SIZE +  ARM_GIC_ICDIPR + (4 * offset))
> >>> +
> >>>  /**
> >>>   *
> >>>   * Return whether the Source interrupt index refers to a shared interrupt (SPI)
> >>> @@ -236,7 +239,7 @@ ArmGicSetInterruptPriority (
> >>>      }
> >>>
> >>>      MmioAndThenOr32 (
> >>> -      GicCpuRedistributorBase + ARM_GIC_ICDIPR + (4 * RegOffset),
> >>> +      IPRIORITY_ADDRESS (GicCpuRedistributorBase, RegOffset),
> >>>        ~(0xff << RegShift),
> >>>        Priority << RegShift
> >>>        );
> >>> --
> >>> 2.17.1
> >>>
> 
> 
> 
> 
> 

  reply	other threads:[~2021-02-24 11:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-23 11:06 [PATCH edk2 v2 1/1] ArmPkg/ArmGic: Fix GICR_IPRIORITYR address wrong issue Ming Huang
2021-02-23 12:42 ` Ard Biesheuvel
2021-02-23 12:58   ` Leif Lindholm
2021-02-24  8:26     ` Ming Huang
2021-02-24 11:49       ` Leif Lindholm [this message]
2021-02-25  3:06         ` [edk2-devel] " Ming Huang
2021-02-23 12:58 ` Heyi Guo
2021-02-23 13:02   ` Leif Lindholm

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=20210224114940.GL1664@vanye \
    --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