Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2786151ybl; Mon, 19 Aug 2019 07:31:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqwi5Fc8Vkv/fejxHNSPzkfB0bparfWknCkVxoBWXgImjLN0d7o+dyayMUBVafv2wUCHGv9H X-Received: by 2002:a17:90a:f995:: with SMTP id cq21mr15471570pjb.27.1566225075821; Mon, 19 Aug 2019 07:31:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566225075; cv=none; d=google.com; s=arc-20160816; b=lIOL1LYtO0HyGLcdCzvpveJlYOx+1el76Iw+66dvRe+gcF35yegDbLrrxQ21+ZJbqn OZ+AfKQ2YWg/0awh5AbPYfhgpiCD222Jmy+NWTAMWy6pknEXoVZAEQIcRM8klMi6znab TLaKx34yg3RtzKm1vSIbyYMZm9bDaw2H/zBvkj6bkf07HyG6Hk14kex9zbxbp/zZGPDY vOn5GvrXTw6StGCBIUaldcMf5f5XU9J/yHI40W4fyzwx4fwyucUBlzzpgE37cE9TmieS Y9TAeGEf/zoD49Y0eC9mQpca3FDmHUlX7EPtGZ2ZejMGOs5hAbsmU8Em7UlEBUMlR3G3 hRpw== 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:from:references:cc:to:subject; bh=3fUYdsJuRbqp+7jy/jjGeERgoFPsGxSAsQkl7Q12wd0=; b=JlgKKOnZS8MGxBUNW/g4XlB+TIMEN5ZwIUNOJZiUaIbsCK6sRV1clB0O+orufBHrhp 844K9Buad6JlGNC0cJKlhpX8Ask0fLHn1t5Bwea+f1+MnQ6IjZGF2bTEQMgQ8LWVkOwQ IvBsofuFcugHWw1WwcRZ3Y5Gi1H7N+DS1YvpZkUsAYBX4GxLeuyAO/6jpPqWhCHQitwe n9CCGNb3Rxo/QC9L2xsrzCSmKsxbPxClSvYNUj2C2PyFJU1Gi/LypvtoIeJ2lV277er1 2Z4tW4os2LFeYAIoz1ECcLx7zlCIChkdE2lSEp8FgUYfgworjoYCEp8h+G+BBZyzNmeu n3DQ== 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i97si8911516pje.47.2019.08.19.07.31.00; Mon, 19 Aug 2019 07:31:15 -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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726987AbfHSO2X (ORCPT + 99 others); Mon, 19 Aug 2019 10:28:23 -0400 Received: from szxga05-in.huawei.com ([45.249.212.191]:4729 "EHLO huawei.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726314AbfHSO2X (ORCPT ); Mon, 19 Aug 2019 10:28:23 -0400 Received: from DGGEMS414-HUB.china.huawei.com (unknown [172.30.72.60]) by Forcepoint Email with ESMTP id A941860674E86CE3D077; Mon, 19 Aug 2019 22:28:19 +0800 (CST) Received: from [127.0.0.1] (10.184.12.158) by DGGEMS414-HUB.china.huawei.com (10.3.19.214) with Microsoft SMTP Server id 14.3.439.0; Mon, 19 Aug 2019 22:28:09 +0800 Subject: Re: [PATCH v2 04/12] irqchip/gic-v3: Add ESPI range support To: Marc Zyngier CC: Thomas Gleixner , Jason Cooper , Julien Thierry , Rob Herring , Lokesh Vutla , John Garry , , "Shameerali Kolothum Thodi" , References: <20190806100121.240767-1-maz@kernel.org> <20190806100121.240767-5-maz@kernel.org> From: Zenghui Yu Message-ID: <9cbd6fc8-3fe9-39fc-10ca-724a1ec06e8d@huawei.com> Date: Mon, 19 Aug 2019 22:25:33 +0800 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:64.0) Gecko/20100101 Thunderbird/64.0 MIME-Version: 1.0 In-Reply-To: <20190806100121.240767-5-maz@kernel.org> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Originating-IP: [10.184.12.158] X-CFilter-Loop: Reflected Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? ITLinesNumber can be '11111', and I saw the following info on my host: "GICv3: 992 SPIs implemented" Thanks, zenghui