Received: by 2002:ad5:4acb:0:0:0:0:0 with SMTP id n11csp4299143imw; Tue, 19 Jul 2022 04:07:48 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vg/bTv8MsO7lxH2DiF82ul1eJFESX6xl8KwkF1p3ojv+H9oLyxKFtMilxaKg2ARkDb7+lY X-Received: by 2002:a05:6830:1cc8:b0:618:ebac:c43f with SMTP id p8-20020a0568301cc800b00618ebacc43fmr13242800otg.45.1658228868709; Tue, 19 Jul 2022 04:07:48 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1658228868; cv=none; d=google.com; s=arc-20160816; b=mlgaLl88HaZhiJE0QJZGcvcPjhQPMpT0RFblhZvMLTKoIfxW1qrrvoQyWdfEw4qGF4 IayED339R+O9OIDxZMXKWgxxkjC+TaGq1xrnzrI49LpERvjkyQWFq2VbYkFRs/7dBoFG H5euO3WejAEkzgTJ010ltsmAVVksCU1b8MGu4f+geKxlhRCcm3vJozx1c02kVxfuhfpf bp6socBtfA9aSdAKLF4ULIDv5K11KIB6/MdMTTcg1US09JNvBhAoVceyWTy4ibTkEaSP AgFIcr3iy4Gb2M3LPCsVUJYmiwCO0DiQ3h5Leq25JEoxANwfTQ7RkNFVI4lLV3+yvMsu 6bFg== 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:dkim-signature; bh=+Mi+PiaKDh2qhoLo366kODSJ9CUSfT/xdvIAf63YF30=; b=XTpTk838GdYwoyW7euomkupyg4CCQh6eyrh896qpZqBALzhdHxNDrnfox+boLDhl/o +2CXGlKpgyq6GeceALHkA6nDy3JVY1IBotnGj/jGY8FfjwQRrt6OJloNaGpDD1XwsRb+ 9oiP78F0dHWBxelk0dc+5uQS5a3UxbzqjlIeQ0xlC4nmwCpMdQH+4WTXNQ0C1C7pIe5W Z8bnox+nz632uQT5Ui07mMjoGe+ZbeQcEUqqzy/9LlcJ8pkC8Thewd+XikgxlgGOZ84V mcLMuktJ83CDvFPLjgpiEr0HZc9VmQNI+KfX/PwbsyzWTHPy6fkqmoX7PVOakVUETW78 Au7Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=d+4ZC1a4; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id bk20-20020a0568081a1400b00339deedd9c4si17834837oib.226.2022.07.19.04.07.34; Tue, 19 Jul 2022 04:07:48 -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; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=d+4ZC1a4; 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=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236479AbiGSKXw (ORCPT + 99 others); Tue, 19 Jul 2022 06:23:52 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47422 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235760AbiGSKXv (ORCPT ); Tue, 19 Jul 2022 06:23:51 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C83B81A079 for ; Tue, 19 Jul 2022 03:23:50 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 592AB60BFE for ; Tue, 19 Jul 2022 10:23:50 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7A0F2C341C6; Tue, 19 Jul 2022 10:23:49 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1658226229; bh=CSbmU+u6na8E3yHadZi8fnz8dH8D9QNQNE1Z3Dx/Raw=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=d+4ZC1a4FU1+S/Y3SSaaBnXmmcYQx2Bepu4la4CcpLIQ7Lze2NDxi/SNK+jFBWylI RyGmoH7VcsgyULZKosW/Rn4SGNZAmmp6kJwr9ApFB2m9Tovv5rZN8tXyDZ5k6Pli16 Z9Zq8yW7E2ycBeR/tPVb5spcNaWKMyN9zruLzOWFpyjstqx+uRToqFDWwm7P6LcbM1 TjMluKFchrH++selvsmv1q+k07W8oE+i8FfwwOhQChkQR2fBbcUXGhde5HVsftFzon rT12Kp34VBd6A8gi6drDdDlXWakNOXMAym+G1uYReG3SdYougY5/aEa14PPQDZqA7A g8XkgoaLa2zVA== Received: from sofa.misterjones.org ([185.219.108.64] helo=why.misterjones.org) by disco-boy.misterjones.org with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.95) (envelope-from ) id 1oDkOJ-008S89-98; Tue, 19 Jul 2022 11:23:47 +0100 Date: Tue, 19 Jul 2022 11:23:47 +0100 Message-ID: <87k089z9ho.wl-maz@kernel.org> From: Marc Zyngier To: Xu Qiang Cc: , , , Subject: Re: [PATCH v2 -next 2/2] irqdomain: Replace revmap_direct_max_irq field with hwirq_max field In-Reply-To: <20220719063641.56541-3-xuqiang36@huawei.com> References: <20220719063641.56541-1-xuqiang36@huawei.com> <20220719063641.56541-3-xuqiang36@huawei.com> 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: 185.219.108.64 X-SA-Exim-Rcpt-To: xuqiang36@huawei.com, tglx@linutronix.de, linux-kernel@vger.kernel.org, weiyongjun1@huawei.com, guohanjun@huawei.com X-SA-Exim-Mail-From: maz@kernel.org X-SA-Exim-Scanned: No (on disco-boy.misterjones.org); SAEximRunCond expanded to false X-Spam-Status: No, score=-7.8 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, 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 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). Thanks, M. -- Without deviation from the norm, progress is not possible.