public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Evan Lloyd <evan.lloyd@arm.com>, "Cohen, Eugene" <eugene@hp.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Heyi Guo <heyi.guo@linaro.org>
Subject: Re: [PATCH] ArmPkg: Fix double GIC EIOR write per interrupt
Date: Sat, 6 Aug 2016 10:24:45 +0200	[thread overview]
Message-ID: <CAKv+Gu9vWFhMFRKz-MvwWD96WifSzPx6TjBUVJN8T1LCZz9fSw@mail.gmail.com> (raw)
In-Reply-To: <20160805165911.14744-1-evan.lloyd@arm.com>

(+ Eugene)

On 5 August 2016 at 18:59,  <evan.lloyd@arm.com> wrote:
> From: Alexei <Alexei.Fedorov@arm.com>
>
> This commit fixes a bug in the GIC v2 and v3 drivers where the GICC_EOIR
> (End Of Interrupt Register) is written twice for a single interrupt.
> GicV(2|3)IrqInterruptHandler() calls the Interrupt Handler and then
> GicV(2|3)EndOfInterrupt() on exit:
>
>  InterruptHandler = gRegisteredInterruptHandlers[GicInterrupt];
>  if (InterruptHandler != NULL) {
>    // Call the registered interrupt handler.
>    InterruptHandler (GicInterrupt, SystemContext);
>  } else {
>    DEBUG ((EFI_D_ERROR, "Spurious GIC interrupt: 0x%x\n", GicInterrupt));
>  }
>
>  GicV2EndOfInterrupt (&gHardwareInterruptV2Protocol, GicInterrupt);
>
> , although gInterrupt->EndOfInterrupt() has already been called by
> InterruptHandler().
>
> The fix moves the EndOfInterrupt() call inside the else case for
> unregistered/spurious interrupts.  This removes a potential race
> condition that might have lost interrupts.
>

I understand that this solves the problem, but it does change the
contract we have with registered interrupt handlers, and we don't know
how this may be used out of tree. I know UEFI only supports polling
for drivers, but are there any other cases (debug?) where we may break
other people's code by doing this?


> Contributed-under: TianoCore Contribution Agreement 1.0
> Signed-off-by: Alexei Fedorov <alexei.fedorov@arm.com>
> Signed-off-by: Evan Lloyd <evan.lloyd@arm.com>
> ---
>
> Code is available at:
> https://github.com/EvanLloyd/tianocore/tree/EOIR_v1
>
>  ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c | 5 ++---
>  ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c | 5 ++---
>  2 files changed, 4 insertions(+), 6 deletions(-)
>
> diff --git a/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c b/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> index 036eb5cd6bf6845dd2b03b62c933c1dedaef7251..34d4be3867647e0fdad7356c949af8cd3ede7164 100644
> --- a/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> +++ b/ArmPkg/Drivers/ArmGic/GicV2/ArmGicV2Dxe.c
> @@ -2,7 +2,7 @@
>
>  Copyright (c) 2009, Hewlett-Packard Company. All rights reserved.<BR>
>  Portions copyright (c) 2010, Apple Inc. All rights reserved.<BR>
> -Portions copyright (c) 2011-2015, ARM Ltd. All rights reserved.<BR>
> +Portions copyright (c) 2011-2016, ARM Ltd. All rights reserved.<BR>
>
>  This program and the accompanying materials
>  are licensed and made available under the terms and conditions of the BSD License
> @@ -178,9 +178,8 @@ GicV2IrqInterruptHandler (
>      InterruptHandler (GicInterrupt, SystemContext);
>    } else {
>      DEBUG ((EFI_D_ERROR, "Spurious GIC interrupt: 0x%x\n", GicInterrupt));
> +    GicV2EndOfInterrupt (&gHardwareInterruptV2Protocol, GicInterrupt);
>    }
> -
> -  GicV2EndOfInterrupt (&gHardwareInterruptV2Protocol, GicInterrupt);
>  }
>
>  //
> diff --git a/ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c b/ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c
> index 106c669fcb8777dfaad609c0ce9f5b572727a3ff..983936f3738a74bb5d5e08e012973df240958a8b 100644
> --- a/ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c
> +++ b/ArmPkg/Drivers/ArmGic/GicV3/ArmGicV3Dxe.c
> @@ -1,6 +1,6 @@
>  /** @file
>  *
> -*  Copyright (c) 2011-2015, ARM Limited. All rights reserved.
> +*  Copyright (c) 2011-2016, ARM Limited. All rights reserved.
>  *
>  *  This program and the accompanying materials
>  *  are licensed and made available under the terms and conditions of the BSD License
> @@ -169,9 +169,8 @@ GicV3IrqInterruptHandler (
>      InterruptHandler (GicInterrupt, SystemContext);
>    } else {
>      DEBUG ((EFI_D_ERROR, "Spurious GIC interrupt: 0x%x\n", GicInterrupt));
> +    GicV3EndOfInterrupt (&gHardwareInterruptV3Protocol, GicInterrupt);
>    }
> -
> -  GicV3EndOfInterrupt (&gHardwareInterruptV3Protocol, GicInterrupt);
>  }
>
>  //
> --
> Guid("CE165669-3EF3-493F-B85D-6190EE5B9759")
>


  reply	other threads:[~2016-08-06  8:24 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05 16:59 [PATCH] ArmPkg: Fix double GIC EIOR write per interrupt evan.lloyd
2016-08-06  8:24 ` Ard Biesheuvel [this message]
2016-08-08 10:25   ` Alexei Fedorov
2016-08-08 10:32     ` Ard Biesheuvel
2016-08-08 10:40       ` Alexei Fedorov
2016-08-08 10:44         ` Ard Biesheuvel
2016-08-08 10:48           ` Alexei Fedorov
2016-08-08 10:49             ` Ard Biesheuvel
2016-08-08 10:56               ` Alexei Fedorov
2016-08-08 10:58                 ` Ard Biesheuvel
2016-08-08 11:06                   ` Alexei Fedorov
2016-08-08 11:08                     ` Ard Biesheuvel
2016-08-08 11:51                       ` Ard Biesheuvel
2016-08-08 13:22                         ` Cohen, Eugene
2016-08-08 13:42                           ` Ard Biesheuvel
2016-08-08 13:50                             ` Ard Biesheuvel
2016-08-10 17:38                               ` Evan Lloyd
2016-08-10 19:34                                 ` Cohen, Eugene
2016-08-10 20:31                                   ` Evan Lloyd
2016-08-10 21:06                                     ` Cohen, Eugene

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=CAKv+Gu9vWFhMFRKz-MvwWD96WifSzPx6TjBUVJN8T1LCZz9fSw@mail.gmail.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