From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.ilvokhin.com (mail.ilvokhin.com [178.62.254.231]) (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 94D37477988 for ; Wed, 1 Apr 2026 16:51:27 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=178.62.254.231 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775062288; cv=none; b=bu/bU5iK7IHcZX0Cm9ag3R///jXXvn08dkiuP7Bmj794IHxBgXMenlmcGhKX8C/fReaxMPNKjR0NeM0z7zJRHQu5SSbIty8onczw/ZbbfC+vZWAUPJ5kcwZYKrWxrh/VF8ZKuCQU57AgvO8bJyuLOJuizR/ecETYvJ7YymhJvT4= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1775062288; c=relaxed/simple; bh=sPT0EmZOtmlkJtbbt1ZELSqVRvLZ7MVBT6Xjodq3b0I=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=GYj9vGoFru2K8vBlUQ2K9HoaIvWuZTJMiaJgu6bzHPnIR68x4qLhaAwnuHJ/VCD0eZnvUoCTrWCjP4RP9eyIJpaGPKwXYUNRtSRIGfKpJk2zfSLs0QSseTXaaY2C01MtnyZjjgOdzIG/Pf9ixCViMGpCCFwzyu6dacD9scbW7bc= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=ilvokhin.com; spf=pass smtp.mailfrom=ilvokhin.com; dkim=pass (1024-bit key) header.d=ilvokhin.com header.i=@ilvokhin.com header.b=mbzsgp2W; arc=none smtp.client-ip=178.62.254.231 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=reject dis=none) header.from=ilvokhin.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ilvokhin.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ilvokhin.com header.i=@ilvokhin.com header.b="mbzsgp2W" Received: from shell.ilvokhin.com (shell.ilvokhin.com [138.68.190.75]) (Authenticated sender: d@ilvokhin.com) by mail.ilvokhin.com (Postfix) with ESMTPSA id E9792BE32C; Wed, 01 Apr 2026 16:51:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ilvokhin.com; s=mail; t=1775062286; bh=Y4YcPD5xbkfDG2X5h0GTQMscWXU/5gt+R1/dptKUS6A=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=mbzsgp2W+AoEebnTUi/8IPiI2rbl0T53ZeWlkVLy92xmA0ncq6MrUZeRC20/TGEDT EgxFvzYPFrjYtrYD0jU8V1OcRJnMCZ07m/PsEnbO7r7SsJJ2nan8b0sGuU7YO/CBfe OJbhVQpLMDkGVhwXMy8qBEfGjJYcss668krPgb8k= Date: Wed, 1 Apr 2026 16:51:24 +0000 From: Dmitry Ilvokhin To: Thomas Gleixner Cc: LKML , x86@kernel.org, Neil Horman , Radu Rendec Subject: Re: [patch v2 13/14] [RFC] genirq/proc: Provide architecture specific binary statistics Message-ID: References: <20260320131108.344376329@kernel.org> <20260320132102.910277045@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260320132102.910277045@kernel.org> 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?