From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 4B90B3195EA for ; Wed, 1 Apr 2026 19:33:38 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775072018; cv=none; b=caRgnWQe/NwwSL1addz3ve0Up8D5UilkpEDmF3cy0bp004SthfDH4I+QDctSyUdBn+gvg/dY9c+aHbItVhRZLpt4pJcknhRC9f3RqwddrBKMnphN6Xwn+1QdkDYg8IaiiDqVemOSlLirBUGIXKAZf9txSbIgkJtIeaqA9iZgauM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775072018; c=relaxed/simple; bh=Z28+4MRUiS8GSAsvem1wYgTGcVJeHlIAtsy7i/A6E2M=; h=From:To:Cc:Subject:In-Reply-To:References:Date:Message-ID: MIME-Version:Content-Type; b=BPwWvN1f3SdtqZrgHHu1FklFgvNsD3aaVljc2fnu1d+LKvxt54UlrjL+uqBo2m7FCRObN6zzNw9tfLgxZg234pTSL0O5o99M65CXFZzWsujN3IXr6t2D4G9WMEgls9xoFdTv3hZG0D/cQoha0/b1Wgg/dwdWhrAkpbcHoIYhQdE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=dBApZs5J; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="dBApZs5J" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 6F66EC19423; Wed, 1 Apr 2026 19:33:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1775072018; bh=Z28+4MRUiS8GSAsvem1wYgTGcVJeHlIAtsy7i/A6E2M=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=dBApZs5Jwk7Ofr1oNhaW7CLF0thsKTpkxjGps/qw6SeKRA+4U5FpTecJvI1VFb/R6 eP3sWIcXSooSfglpzViQhKaKFvB5b2EAHvFMpmsiEhFu9Ai6szPFAOfHNBqK0aQ7v5 XoPet9naxl4AAq/FI99JpC3ke4yooKoYXApH8sF51rqi/VRfT5PaqXRFRsYlH4vvMS Ca+/3Utl29mxSP0ogHZciOVJOcm1rKQE6P8MOxoo34ZtfeY0CrznuKAUzxKh1hHglJ 3nJb60ju7mXCHkSQpScIeu4qIOFA8p4Ztt+PJaMkVrTVQ/aUmq2muYJQtzmB+mk2Q8 4xkH8klli9ERg== From: Thomas Gleixner To: Dmitry Ilvokhin Cc: LKML , x86@kernel.org, Neil Horman , Radu Rendec Subject: Re: [patch v2 13/14] [RFC] genirq/proc: Provide architecture specific binary statistics In-Reply-To: References: <20260320131108.344376329@kernel.org> <20260320132102.910277045@kernel.org> Date: Wed, 01 Apr 2026 21:33:34 +0200 Message-ID: <87wlyq79wx.ffs@tglx> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain On Wed, Apr 01 2026 at 16:51, Dmitry Ilvokhin wrote: > On Fri, Mar 20, 2026 at 02:22:29PM +0100, Thomas Gleixner wrote: >> Provide a binary statistics interface similar to the per device and per CPU >> interfaces to access the architecture specific interrupt statistics. >> >> The architecture has to select it in Kconfig and provide an accessor to the >> per CPU interrupt information and the number of architecture specific >> entries. >> >> The entries are ordered by a numerical index starting from 0, which >> corresponds to the ordering of those interrupts in /proc/interrupt. The > > This mapping is fragile. The IRQ_COUNT_* enum is kernel-internal, > config-dependent, and not exposed to userspace. Correlating indices to > names via /proc/interrupts line positions relies on both interfaces > skipping the same entries, which is not enforced. > > Would it make sense to expose the short symbol name (e.g. "NMI", "LOC", > "TLB") alongside the index, or provide a companion file that lists them? Yes. There should be a file which describes the indices on the machine.