From: Thomas Gleixner <tglx@linutronix.de>
To: "enlin.mu" <18001123162@163.com>,
18001123162@web.codeaurora.org, enlin.mu@unisoc.com,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org, hch@lst.de
Subject: Re: [PATCH] proc/softirqs: change softirqs info from possile_cpu to online_cpu
Date: Tue, 12 Nov 2024 03:16:13 +0100 [thread overview]
Message-ID: <87ed3hnqmq.ffs@tglx> (raw)
In-Reply-To: <20241108162225.19401-1-18001123162@163.com>
On Sat, Nov 09 2024 at 00:22, enlin mu wrote:
> From: Enlin Mu <enlin.mu@unisoc.com>
>
> like /proc/interrupts,/proc/softirqs which shows
> the number of softirq for each online CPU
This changes the output format of a file which is used by various
tools, i.e. this is an ABI change.
Did you validate that none of these tools relies on consecutive CPU
numbers even when CPUs in the middle of the number space are offline?
Thanks,
tglx
prev parent reply other threads:[~2024-11-12 2:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 16:22 [PATCH] proc/softirqs: change softirqs info from possile_cpu to online_cpu enlin.mu
2024-11-12 2:16 ` Thomas Gleixner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ed3hnqmq.ffs@tglx \
--to=tglx@linutronix.de \
--cc=18001123162@163.com \
--cc=18001123162@web.codeaurora.org \
--cc=akpm@linux-foundation.org \
--cc=enlin.mu@unisoc.com \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox