mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Vladimir Murzin <vladimir.murzin@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, tglx@kernel.org, radu@rendec.net
Subject: Re: [PATCH] irqchip/gic-v3: Ensure change to DS is visible
Date: Wed, 30 Sep 2026 19:55:35 +0100	[thread overview]
Message-ID: <87o6de36xk.wl-maz@kernel.org> (raw)
In-Reply-To: <20260930161123.46368-1-vladimir.murzin@arm.com>

On Wed, 30 Sep 2026 17:11:23 +0100,
Vladimir Murzin <vladimir.murzin@arm.com> wrote:
> 
> Sashiko reported missing GIC synchronization when the
> FLAGS_WORKAROUND_INSECURE path modifies DS. Specifically, an immediate
> read of the DS state after the write might not observe the effect of
> that write, which can lead to misreporting the DS state.
> 
> Updates to the DS bit are tracked by RWP, so poll it after the write
> before proceeding to read back the DS state.
> 
> Signed-off-by: Vladimir Murzin <vladimir.murzin@arm.com>
> ---
>  drivers/irqchip/irq-gic-v3.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c
> index 6e1fa5b247fc..181f6eb11732 100644
> --- a/drivers/irqchip/irq-gic-v3.c
> +++ b/drivers/irqchip/irq-gic-v3.c
> @@ -164,6 +164,7 @@ static inline bool gic_dist_security_disabled(void)
>  
>  static bool cpus_have_security_disabled __ro_after_init;
>  static bool cpus_have_group0 __ro_after_init;
> +static void gic_dist_wait_for_rwp(void);
>  
>  static void __init gic_prio_init(void)
>  {
> @@ -179,6 +180,7 @@ static void __init gic_prio_init(void)
>  			val = readl_relaxed(gic_data.dist_base + GICD_CTLR);
>  			val |= GICD_CTLR_DS;
>  			writel_relaxed(val, gic_data.dist_base + GICD_CTLR);
> +			gic_dist_wait_for_rwp();
>  
>  			ds = gic_dist_security_disabled();
>  			if (ds)

Ah, well spotted. FWIW:

Reviewed-by: Marc Zyngier <maz@kernel.org>

	M.

-- 
Jazz isn't dead. It just smells funny.

      reply	other threads:[~2026-09-30 18:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 16:11 Vladimir Murzin
2026-09-30 18:55 ` Marc Zyngier [this message]

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-all 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=87o6de36xk.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=radu@rendec.net \
    --cc=tglx@kernel.org \
    --cc=vladimir.murzin@arm.com \
    /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

all inboxes | Powered by JetHome®