linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Zenghui Yu <yuzenghui@huawei.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <lpieralisi@kernel.org>,
	<tglx@linutronix.de>, <wanghaibin.wang@huawei.com>
Subject: Re: [PATCH] irqchip/gic-v5: Remove the redundant ITS cache invalidation
Date: Wed, 03 Sep 2025 07:21:07 +0100	[thread overview]
Message-ID: <87y0qwys30.wl-maz@kernel.org> (raw)
In-Reply-To: <20250903023319.1820-1-yuzenghui@huawei.com>

On Wed, 03 Sep 2025 03:33:19 +0100,
Zenghui Yu <yuzenghui@huawei.com> wrote:
> 
> An ITS cache invalidation has been performed immediately after programming
> the L2 DTE in gicv5_its_device_register(). No need to perform it again
> right after a successful gicv5_its_device_register().

Indeed. And this call doesn't check it's been successful either.

> 
> Remove it.
> 
> Signed-off-by: Zenghui Yu <yuzenghui@huawei.com>
> ---
>  drivers/irqchip/irq-gic-v5-its.c | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-gic-v5-its.c b/drivers/irqchip/irq-gic-v5-its.c
> index 2fb58d76f521..554485f0be1f 100644
> --- a/drivers/irqchip/irq-gic-v5-its.c
> +++ b/drivers/irqchip/irq-gic-v5-its.c
> @@ -768,8 +768,6 @@ static struct gicv5_its_dev *gicv5_its_alloc_device(struct gicv5_its_chip_data *
>  		goto out_dev_free;
>  	}
>  
> -	gicv5_its_device_cache_inv(its, its_dev);
> -
>  	its_dev->its_node = its;
>  
>  	its_dev->event_map = (unsigned long *)bitmap_zalloc(its_dev->num_events, GFP_KERNEL);

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

	M.

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


      reply	other threads:[~2025-09-03  6:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-03  2:33 [PATCH] irqchip/gic-v5: Remove the redundant ITS cache invalidation Zenghui Yu
2025-09-03  6:21 ` 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=87y0qwys30.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=wanghaibin.wang@huawei.com \
    --cc=yuzenghui@huawei.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;
as well as URLs for NNTP newsgroup(s).