Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4484895imw; Tue, 19 Jul 2022 07:29:16 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uYOHgmjwwhmDthLfw4RBro1YC4w3CwzFAbBMsmuqr1b2nBAsTt2A8bZcWdOxAFUmVXijHI X-Received: by 2002:a05:6870:6389:b0:10c:10df:e0cc with SMTP id t9-20020a056870638900b0010c10dfe0ccmr18209076oap.227.1658240956274; Tue, 19 Jul 2022 07:29:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658240956; cv=none; d=google.com; s=arc-20160816; b=fRSviFzchnAZP2SPhsKgW4sbL5biNkmM4xzD0yqYof4VH2BqqBb5kNRa3dlOYBPYCD E6PgAqhevXOa4cYT90i58xkwJQDgEW6EpgldUGGkB8zCEnj+tXRXRqXmaWU/tulwL7W0 qeeacrKcODKTtj91dE5GoP7tHDG13jBjgkKL9uStiLcUXjZVK/tcmeMY8ioZ33vUSzPK KRHiDb79BIfgywpIIiEp56E1eJ4cKufovWylbfXhecUJdQ7LUjqY///EvBhwH1iaZRGu ovOnEXZzndOE8rpO9tcPQWKKnjpyEJeyMGI5SIPAO2WtniRLDug3S4uYKsUHmfq+8G2I s+rw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:mime-version:content-transfer-encoding :content-language:accept-language:references:message-id:date :thread-index:thread-topic:subject:cc:to:from; bh=XzHSjLdLyY3lZxre27JYk76a6ZpC0wBDyUN0b3teJW4=; b=AH8MJT5WefhJUT/xoCRjXal4r24mBm1OY5XYMVfyYK3zyBblnDyCuCj/KtIlekoVt/ gHv7unVHxlau90oxgVu2vynssZM+Cht138PNAyTFJOu95NAeoQNM+/G9C0qHZNMwxWBc p3WKyui9vCwCR4P58vO/smqt5jar5qEjgxS+RGZHxQ4u8bHFIo6vPNFE5Xsyz3Dk/tEb ackm0uasdksfSLxcg2Ml9P7LV/G9RO3T/ZTEipbMIydx72agF5VlQooKtGetxrKwQGes 46cV9q7uJlKu3cs8oYQ1kZfaWliuDj7I5and8sgPTb2REOy3imTUcHEDxR5VZ1ruLiCx gUtg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bx2-20020a056830600200b006169c920cbesi15707060otb.197.2022.07.19.07.29.03; Tue, 19 Jul 2022 07:29:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=huawei.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235311AbiGSOPz convert rfc822-to-8bit (ORCPT + 99 others); Tue, 19 Jul 2022 10:15:55 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235080AbiGSOP3 (ORCPT ); Tue, 19 Jul 2022 10:15:29 -0400 Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [45.249.212.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D73C4E854 for ; Tue, 19 Jul 2022 06:44:18 -0700 (PDT) Received: from dggpemm500023.china.huawei.com (unknown [172.30.72.54]) by szxga01-in.huawei.com (SkyGuard) with ESMTP id 4LnKk46619zjX4T; Tue, 19 Jul 2022 21:41:32 +0800 (CST) Received: from dggpemm100001.china.huawei.com (7.185.36.93) by dggpemm500023.china.huawei.com (7.185.36.83) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 19 Jul 2022 21:44:15 +0800 Received: from kwepemi500012.china.huawei.com (7.221.188.12) by dggpemm100001.china.huawei.com (7.185.36.93) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2375.24; Tue, 19 Jul 2022 21:44:15 +0800 Received: from kwepemi500012.china.huawei.com ([7.221.188.12]) by kwepemi500012.china.huawei.com ([7.221.188.12]) with mapi id 15.01.2375.024; Tue, 19 Jul 2022 21:44:15 +0800 From: "xuqiang (M)" To: Marc Zyngier CC: "tglx@linutronix.de" , "linux-kernel@vger.kernel.org" , "weiyongjun (A)" , "Guohanjun (Hanjun Guo)" Subject: Re: [PATCH v2 -next 2/2] irqdomain: Replace revmap_direct_max_irq field with hwirq_max field Thread-Topic: [PATCH v2 -next 2/2] irqdomain: Replace revmap_direct_max_irq field with hwirq_max field Thread-Index: AQHYmzpBZhMLU8dgIUSvhshLWJNuNw== Date: Tue, 19 Jul 2022 13:44:15 +0000 Message-ID: References: <20220719063641.56541-1-xuqiang36@huawei.com> <20220719063641.56541-3-xuqiang36@huawei.com> <87k089z9ho.wl-maz@kernel.org> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.174.179.28] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Spam-Status: No, score=-4.2 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED, SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 在 2022/7/19 18:24, Marc Zyngier 写道: > On Tue, 19 Jul 2022 07:36:41 +0100, > Xu Qiang wrote: >> In commit "4f86a06e2d6e irqdomain: Make normal and nomap irqdomains exclusive", >> use revmap_size field instead of revmap_direct_max_irq. revmap_size field >> originally indicates the maximum hwirq of linear Mapping. This results in >> revmap_size having two different layers of meaning that can be confusing. >> >> This patch optimization point is to solve this confusion point. During >> direct mapping, the values of hwirq_max and revmap_direct_max_irq are the same >> and have the same meanings. They both indicate the maximum hwirq supported by >> direct Mapping. The optimization method is to delete revmap_direct_max_irq >> field and use hwirq_max instead of revmap_direct_max_irq. >> >> Signed-off-by: Xu Qiang > You keep referencing revmap_direct_max_irq, which is long gone. > > How about instead: > > > NOMAP irq domains use the revmap_size field to indicate the maximum > hwirq number the domain accepts. This is a bit confusing as > revmap_size is usually used to indicate the size of the revmap array, > which a NOMAP domain doesn't have. > > Instead, use the hwirq_max field which has the correct semantics, and > keep revmap_size to 0 for a NOMAP domain. > > > If you agree with this, please say so (no need to respin for this). Yes, I agree. Thanks, Xu. > > Thanks, > > M. >