From: David Wang <00107082@163.com>
To: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me
Cc: linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: nvme interrupt counters got reset after suspend/resume
Date: Wed, 19 Mar 2025 23:39:10 +0800 [thread overview]
Message-ID: <20250319153910.18684-1-00107082@163.com> (raw)
Hi,
I noticed that on my system, the counters from /proc/interrupts
for nvme got reset after I suspend and then resume the system.
For example, before `systemctl suspend`:
$ cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
...
38: 0 0 0 22 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 0-edge nvme0q0
39: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:22:00.0 0-edge enp34s0
40: 78 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 1-edge nvme0q1
41: 0 147 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 2-edge nvme0q2
42: 0 0 13 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 3-edge nvme0q3
43: 0 0 0 9 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 4-edge nvme0q4
44: 0 0 0 0 87 0 0 0 IR-PCI-MSIX-0000:25:00.0 5-edge nvme0q5
45: 0 0 0 0 0 112 0 0 IR-PCI-MSIX-0000:25:00.0 6-edge nvme0q6
46: 0 0 0 0 0 0 12 0 IR-PCI-MSIX-0000:25:00.0 7-edge nvme0q7
47: 0 0 0 0 0 0 0 8 IR-PCI-MSIX-0000:25:00.0 8-edge nvme0q8
And right after resume the system, values are reset to 0s:
$ cat /proc/interrupts
CPU0 CPU1 CPU2 CPU3 CPU4 CPU5 CPU6 CPU7
...
38: 0 0 0 21 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 0-edge nvme0q0
39: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:22:00.0 0-edge enp34s0
40: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 1-edge nvme0q1
41: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 2-edge nvme0q2
42: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 3-edge nvme0q3
43: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 4-edge nvme0q4
44: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 5-edge nvme0q5
45: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 6-edge nvme0q6
46: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 7-edge nvme0q7
47: 0 0 0 0 0 0 0 0 IR-PCI-MSIX-0000:25:00.0 8-edge nvme0q8
This does not happend to counters for other interrupts on my system.
Not sure whether this is designed explicitly this way, or happended to be this way to make suspend/resume work,
or there is some bug behind this.
Just bring this up for discussion since I failed to find any discussion about it.
Thanks
David.
next reply other threads:[~2025-03-19 15:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 15:39 David Wang [this message]
2025-03-19 15:57 ` nvme interrupt counters got reset after suspend/resume Keith Busch
2025-03-19 16:23 ` David Wang
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=20250319153910.18684-1-00107082@163.com \
--to=00107082@163.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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