All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Mikko Perttunen <mperttunen@nvidia.com>,
	tglx@linutronix.de, jason@lakedaemon.net
Cc: linux-kernel@vger.kernel.org, talho@nvidia.com,
	aniruddhab@nvidia.com, Matt Craighead <mcraighead@nvidia.com>
Subject: Re: [PATCH] irqchip/gic: Don't write to GICD_ICFGR0
Date: Thu, 6 Apr 2017 10:26:58 +0100	[thread overview]
Message-ID: <3c8d9248-39c2-9b70-7a41-0b51e6ba5a3c@arm.com> (raw)
In-Reply-To: <1491466631-11206-1-git-send-email-mperttunen@nvidia.com>

On 06/04/17 09:17, Mikko Perttunen wrote:
> From: Matt Craighead <mcraighead@nvidia.com>
> 
> According to the GICv2 specification, the GICD_ICFGR0,
> or GIC_DIST_CONFIG[0] register is read-only. Therefore
> avoid writing to it.

Have you verified that this also applies to pre-v2 GICs?

> 
> Signed-off-by: Matt Craighead <mcraighead@nvidia.com>
> [mperttunen@nvidia.com: commit message rewritten]
> Signed-off-by: Mikko Perttunen <mperttunen@nvidia.com>
> ---
>  drivers/irqchip/irq-gic.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/irqchip/irq-gic.c b/drivers/irqchip/irq-gic.c
> index 1b1df4f770bd..d9c0000050e0 100644
> --- a/drivers/irqchip/irq-gic.c
> +++ b/drivers/irqchip/irq-gic.c
> @@ -609,7 +609,7 @@ void gic_dist_restore(struct gic_chip_data *gic)
>  
>  	writel_relaxed(GICD_DISABLE, dist_base + GIC_DIST_CTRL);
>  
> -	for (i = 0; i < DIV_ROUND_UP(gic_irqs, 16); i++)
> +	for (i = 1; i < DIV_ROUND_UP(gic_irqs, 16); i++)
>  		writel_relaxed(gic->saved_spi_conf[i],
>  			dist_base + GIC_DIST_CONFIG + i * 4);
>  
> @@ -699,7 +699,7 @@ void gic_cpu_restore(struct gic_chip_data *gic)
>  	}
>  
>  	ptr = raw_cpu_ptr(gic->saved_ppi_conf);
> -	for (i = 0; i < DIV_ROUND_UP(32, 16); i++)
> +	for (i = 1; i < DIV_ROUND_UP(32, 16); i++)
>  		writel_relaxed(ptr[i], dist_base + GIC_DIST_CONFIG + i * 4);

Assuming that the above stands for all GICs, it feels like there is room
for simplification here. But you haven't dealt with the save side, so
what's the point?

Also, you're missing out some other stuff which is (by definition) RO as
well, such as the target registers for SGIs and PPIs. Finally, there is
the question of the allocated memory for these registers.

Overall, I'm not sure what this patch is trying to achieve. It doesn't
fix a bug, and is not complete enough to do something useful (even
though it would only be saving a handful of bytes).

Maybe you can explain what you're trying to do here?

Thanks,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2017-04-06  9:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-06  8:17 [PATCH] irqchip/gic: Don't write to GICD_ICFGR0 Mikko Perttunen
2017-04-06  9:26 ` Marc Zyngier [this message]
2017-04-07  6:49   ` Mikko Perttunen
2017-04-07  7:32     ` Marc Zyngier
2017-04-10 10:32       ` Mikko Perttunen

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=3c8d9248-39c2-9b70-7a41-0b51e6ba5a3c@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=aniruddhab@nvidia.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mcraighead@nvidia.com \
    --cc=mperttunen@nvidia.com \
    --cc=talho@nvidia.com \
    --cc=tglx@linutronix.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.