Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4411082pxf; Tue, 30 Mar 2021 07:13:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy2TjorcTc0IrFMXVaha24Si2d+uCqOybXJHQ/QKlvKEbd90jCB68UVhUyt7DLdsMMarUV0 X-Received: by 2002:a05:6402:22b5:: with SMTP id cx21mr34002298edb.27.1617113618823; Tue, 30 Mar 2021 07:13:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617113618; cv=none; d=google.com; s=arc-20160816; b=NN0A5DRIo4XJEoSSgduyv9/fWXUAtVVwPcRlaiqcLbygeiA5P0q3oa67BCv6dBiDeM vhl2KUOS520sQJTLYCiOwIRtneYFNmU4aSNZ53btq4lDvDS705sxNSy6jqGdF1iTs+9D W/j/A4ElbpYoiFZALooiIGSInfFowKTRA55JgkHI0irt2BItFpIv2E0q4Fd5PrlTeBLN 517oYUkThAe8SnZ4ue61QLBCFr9n/GkAnHz98MM0G4Y4V92cn+ZPUrp5ScuEwo/3KMw3 NbIxyqyHSb2xq4mvxw1xYXglXYqnr4sNWxBIdZKCnoKhfQnRKC0YD1QqSG5x5S73N6YY yrnQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:user-agent:references:in-reply-to :subject:cc:to:from:message-id:date; bh=JfgJm0xxj4z1HliQGPO6Uk48t/lgFWg7823vj7dqLv4=; b=eXWuIFP7Q98n+B0zhtADABNlFj4zSMDt1TJ+IcWzaKDh1PfuodL7gLZdFxKxEc6PsS bBl4R2lV9Eg9sj7iXPLuWjvcV9Dlw7aTDo/YroT3eBrOO2kfA9Qni2F+LXxjuHkNbMwr m+U5s/F4vmnllx+VCMg9rgkk2KyPdh0rairWZnzkXrxrjunBBlFs0mWmLwGsfTcTeqN3 +HunNtlihrnzqua+hys+oyyW/vxBLuozFrAsW0tLuvzBP6isOAC6tLlHBSJBeMn+sYoK fbeaO5wUpks5XGQ0dHkS7ldsy4p6BFxhOK58TWCpgViV12QrxqhnyxR8KYq3IYo36hf4 IECg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id u21si15905200ejt.396.2021.03.30.07.13.16; Tue, 30 Mar 2021 07:13:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231694AbhC3OMO (ORCPT + 99 others); Tue, 30 Mar 2021 10:12:14 -0400 Received: from mail.kernel.org ([198.145.29.99]:42670 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232017AbhC3OLo (ORCPT ); Tue, 30 Mar 2021 10:11:44 -0400 Received: from disco-boy.misterjones.org (disco-boy.misterjones.org [51.254.78.96]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 9B90C619CA; Tue, 30 Mar 2021 14:11:44 +0000 (UTC) Received: from 78.163-31-62.static.virginmediabusiness.co.uk ([62.31.163.78] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from ) id 1lRF5q-004hEK-QL; Tue, 30 Mar 2021 15:11:42 +0100 Date: Tue, 30 Mar 2021 15:11:42 +0100 Message-ID: <87eefwrash.wl-maz@kernel.org> From: Marc Zyngier To: Lorenzo Pieralisi Cc: Lecopzer Chen , linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, tglx@linutronix.de, lecopzer@gmail.com, yj.chiang@mediatek.com, Julien Thierry Subject: Re: [PATCH] irqchip/gic-v3: Fix IPRIORITYR can't perform byte operations in GIC-600 In-Reply-To: <20210330130637.GA26263@lpieralisi> References: <20210330100619.24747-1-lecopzer.chen@mediatek.com> <87o8f1q6c6.wl-maz@kernel.org> <20210330110546.GA24881@lpieralisi> <20210330130637.GA26263@lpieralisi> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (=?UTF-8?B?R29qxY0=?=) APEL-LB/10.8 EasyPG/1.0.0 Emacs/27.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SA-Exim-Connect-IP: 62.31.163.78 X-SA-Exim-Rcpt-To: lorenzo.pieralisi@arm.com, lecopzer.chen@mediatek.com, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, tglx@linutronix.de, lecopzer@gmail.com, yj.chiang@mediatek.com, julien.thierry.kdev@gmail.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 30 Mar 2021 14:06:37 +0100, Lorenzo Pieralisi wrote: > > On Tue, Mar 30, 2021 at 12:05:46PM +0100, Lorenzo Pieralisi wrote: > > On Tue, Mar 30, 2021 at 11:33:13AM +0100, Marc Zyngier wrote: > > > [+Lorenzo, +Julien on an actual email address] > > > > > > On Tue, 30 Mar 2021 11:06:19 +0100, > > > Lecopzer Chen wrote: > > > > > > > > When pseudo-NMI enabled, register_nmi() set priority of specific IRQ > > > > by byte ops, and this doesn't work in GIC-600. > > > > > > > > We have asked ARM Support [1]: > > > > > Please refer to following description in > > > > > "2.1.2 Distributor ACE-Lite slave interface" of GIC-600 TRM for > > > > > the GIC600 ACE-lite slave interface supported sizes: > > > > > "The GIC-600 only accepts single beat accesses of the sizes for > > > > > each register that are shown in the Programmers model, > > > > > see Chapter 4 Programmer's model on page 4-102. > > > > > All other accesses are rejected and given either an > > > > > OKAY or SLVERR response that is based on the GICT_ERR0CTLR.UE bit.". > > > > > > > > Thus the register needs to be written by double word operation and > > > > the step will be: read 32bit, set byte and write it back. > > > > > > > > [1] https://services.arm.com/support/s/case/5003t00001L4Pba > > > > > > You do realise that this link: > > > > > > - is unusable for most people as it is behind a registration interface > > > - discloses confidential information to other people > > > > > > I strongly suggest you stop posting such links. > > > > > > > > > > > Signed-off-by: Lecopzer Chen > > > > --- > > > > drivers/irqchip/irq-gic-v3.c | 13 ++++++++++++- > > > > 1 file changed, 12 insertions(+), 1 deletion(-) > > > > > > > > diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c > > > > index eb0ee356a629..cfc5a6ad30dc 100644 > > > > --- a/drivers/irqchip/irq-gic-v3.c > > > > +++ b/drivers/irqchip/irq-gic-v3.c > > > > @@ -440,10 +440,21 @@ static void gic_irq_set_prio(struct irq_data *d, u8 prio) > > > > { > > > > void __iomem *base = gic_dist_base(d); > > > > u32 offset, index; > > > > + u32 val, prio_offset_mask, prio_offset_shift; > > > > > > > > offset = convert_offset_index(d, GICD_IPRIORITYR, &index); > > > > > > > > - writeb_relaxed(prio, base + offset + index); > > > > + /* > > > > + * GIC-600 memory mapping register doesn't support byte opteration, > > > > + * thus read 32-bits from register, set bytes and wtire back to it. > > > > + */ > > > > + prio_offset_shift = (index & 0x3) * 8; > > > > + prio_offset_mask = GENMASK(prio_offset_shift + 7, prio_offset_shift); > > > > + index &= ~0x3; > > > > + val = readl_relaxed(base + offset + index); > > > > + val &= ~prio_offset_mask; > > > > + val |= prio << prio_offset_shift; > > > > + writel_relaxed(val, base + offset + index); > > > > } > > > > > > > > static u32 gic_get_ppi_index(struct irq_data *d) > > > > > > From the architecture spec: > > > > > > > > > 11.1.3 GIC memory-mapped register access > > > > > > In any system, access to the following registers must be supported: > > > > > > [...] > > > * Byte accesses to: > > > - GICD_IPRIORITYR. > > > - GICD_ITARGETSR. > > > - GICD_SPENDSGIR. > > > - GICD_CPENDSGIR. > > > - GICR_IPRIORITYR. > > > > > > > > > So if GIC600 doesn't follow this architectural requirement, this is a > > > HW erratum, and I want an actual description of the HW issue together > > > with an erratum number. > > > > > > Lorenzo, can you please investigate on your side? > > > > Sure - I will look into it and report back. > > Checked - I don't think this patch is needed so it should be dropped and > a follow-up discussion can continue in the relevant/appropriate forum - > if there is anything left to discuss. Thanks for having had a look. This really smells like an integration issue rather than an actual GIC bug. Lecopzer, please check with your HW people and potentially ARM, as I think you are looking at the wrong problem. Thanks, M. -- Without deviation from the norm, progress is not possible.