Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp3796803ybl; Tue, 20 Aug 2019 02:21:54 -0700 (PDT) X-Google-Smtp-Source: APXvYqzPUpBLoR6TJo9E8CR585nrJCUChkOkLfvIuNC7KdSwl/uQUpP3LjDFCXrRa4CZ+LGqlMaA X-Received: by 2002:a63:195f:: with SMTP id 31mr24207865pgz.225.1566292914156; Tue, 20 Aug 2019 02:21:54 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566292914; cv=none; d=google.com; s=arc-20160816; b=Hw0HmKtBPH0hzqRYiinZsO4aZksQ2JcJThG5+bOptgj7jPH4J/2yb0ghyXkTkEEq+4 kZV2rQnJU3KXpNeyqgxDfO6KgpaNBBGGd8/4x9yu92+3974KxDt1h+uoC3iTH3jmBDz7 OZsVzjHL3nxjLkRQIqOiLGGgRWkfAnVROgelRfsYKzDLQrTg4OY55Mi2LxsWUW0faS5m gVZMaFm4lghJStRQwPB3Qy3w0YGaDFm05FXHFvonvXETnsV12pvwjW+DbD7z1cw2rNLB gfTrQdntzVNWar3ialUnw7TwDoTZyxqPycVzDpvt1JN3X7hlOaB14kpLXckOiAATBL5e p18A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject; bh=GgVc+dIbyoa/0iJvcGGY8YxijMND6AX7rHH+EsODX/U=; b=Ruk8iOv6laSPE7DHbSOT25/otnDMYcytTYgnN/85MDRBFSobT8u6TAXPGwX+wjBCyG cVntvRNG0/g3M4s/wH2llr1W/yjuXZQAY2Se6m3fA3Wo8mk11yFe5DW8jHcZlEWbnaC9 8CAJe2cmZcUGNLQdEEuwZtvPFxeHORjddk/fuGRx4MG7Ov+rxXpSrPC4+ppkB4oheV3O kk3+mgx4kp/vjtmsEw8j+KPXIdU/93bAJxqO9ZfHlImAHnUq8cajgh5Alp/ICCezUvfj csQ5Da1a+u7gjvQFmoF5eApvpHqnH5R27QFC50LFZL2zuHZxHxTwy/pDBovjau9LmNj5 Ra4g== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f131si11661137pgc.265.2019.08.20.02.21.39; Tue, 20 Aug 2019 02:21:54 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729570AbfHTJTB (ORCPT + 99 others); Tue, 20 Aug 2019 05:19:01 -0400 Received: from foss.arm.com ([217.140.110.172]:37114 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728414AbfHTJTA (ORCPT ); Tue, 20 Aug 2019 05:19:00 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D5821344; Tue, 20 Aug 2019 02:18:59 -0700 (PDT) Received: from [10.1.197.61] (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 57B3B3F706; Tue, 20 Aug 2019 02:18:58 -0700 (PDT) Subject: Re: [PATCH v2 04/12] irqchip/gic-v3: Add ESPI range support To: Zenghui Yu Cc: Thomas Gleixner , Jason Cooper , Julien Thierry , Rob Herring , Lokesh Vutla , John Garry , linux-kernel@vger.kernel.org, Shameerali Kolothum Thodi , linux-arm-kernel@lists.infradead.org References: <20190806100121.240767-1-maz@kernel.org> <20190806100121.240767-5-maz@kernel.org> <9cbd6fc8-3fe9-39fc-10ca-724a1ec06e8d@huawei.com> From: Marc Zyngier Organization: Approximate Message-ID: <30fe07e9-0670-d755-2173-dc71549a797b@kernel.org> Date: Tue, 20 Aug 2019 10:18:56 +0100 User-Agent: Mozilla/5.0 (X11; Linux aarch64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <9cbd6fc8-3fe9-39fc-10ca-724a1ec06e8d@huawei.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/08/2019 15:25, Zenghui Yu wrote: > Hi Marc, > > On 2019/8/6 18:01, Marc Zyngier wrote: >> Add the required support for the ESPI range, which behave exactly like >> the SPIs of old, only with new funky INTIDs. >> >> Signed-off-by: Marc Zyngier >> --- >> drivers/irqchip/irq-gic-v3.c | 85 ++++++++++++++++++++++++------ >> include/linux/irqchip/arm-gic-v3.h | 17 +++++- >> 2 files changed, 85 insertions(+), 17 deletions(-) >> >> diff --git a/drivers/irqchip/irq-gic-v3.c b/drivers/irqchip/irq-gic-v3.c >> index db3bdedd7241..1ca4dde32034 100644 >> --- a/drivers/irqchip/irq-gic-v3.c >> +++ b/drivers/irqchip/irq-gic-v3.c >> @@ -51,13 +51,16 @@ struct gic_chip_data { >> u32 nr_redist_regions; >> u64 flags; >> bool has_rss; >> - unsigned int irq_nr; >> struct partition_desc *ppi_descs[16]; >> }; >> >> static struct gic_chip_data gic_data __read_mostly; >> static DEFINE_STATIC_KEY_TRUE(supports_deactivate_key); >> >> +#define GIC_ID_NR (1U << GICD_TYPER_ID_BITS(gic_data.rdists.gicd_typer)) >> +#define GIC_LINE_NR GICD_TYPER_SPIS(gic_data.rdists.gicd_typer) > > This indicates the maximum SPI INTID that the GIC implementation > supports, should we restrict it to no more than 1020? I guess we could write it as max(GICD_TYPER_SPIS(...), 1020), but that's not a material change (the registers backing the special range do exist). > ITLinesNumber can be '11111', and I saw the following info on my host: > "GICv3: 992 SPIs implemented" Yeah, the above should fix the print. Thanks, M. -- Jazz is not dead, it just smells funny...