LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gautam Menghani <gautam@linux.ibm.com>
To: Timothy Pearson <tpearson@raptorengineering.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Ritesh Harjani <ritesh.list@gmail.com>
Subject: Re: [BUG] Continuously increasing spurious interrupts inside pSeries guest on PowerNV host
Date: Tue, 1 Sep 2026 11:45:20 +0530	[thread overview]
Message-ID: <apZteAd6mDv9URaD@Gautams-MacBook-Pro.local> (raw)
In-Reply-To: <582904882.11159.1786719390349.JavaMail.zimbra@raptorengineeringinc.com>

On Fri, Aug 14, 2026 at 09:56:30AM -0500, Timothy Pearson wrote:
> With kernel 6.12 (Debian stable) we see a continuously increasing spurious interrupt count inside a pSeries guest running on a PowerNV host:
> 
> cat /proc/interrupts
>            CPU0
>  16:          0  XIVE-IPI   0 Edge      IPI-0
>  17:          0  XIVE-IRQ 4096 Edge      RAS_EPOW
>  21:          2  XIVE-IRQ 4353 Edge      hvc_console
>  23:          0  XIVE-IRQ 4097 Edge      RAS_HOTPLUG
>  24:          0  pSeries-PCI-MSI   0 Edge      virtio0-config
>  25:      50995  pSeries-PCI-MSI   1 Edge      virtio0-input.0
>  26:      45569  pSeries-PCI-MSI   2 Edge      virtio0-output.0
>  27:          0  pSeries-PCI-MSI 16384 Edge      virtio1-config
>  28:          6  pSeries-PCI-MSI 16385 Edge      virtio1-input
> LOC:       5781   Local timer interrupts for timer event device
> BCT:          0   Broadcast timer interrupts for timer event device
> LOC:          2   Local timer interrupts for others
> SPU:     449927   Spurious interrupts
> PMI:          0   Performance monitoring interrupts
> MCE:          0   Machine check exceptions
> NMI:          0   System Reset interrupts
> WDG:          0   Watchdog soft-NMI interrupts
> DBL:          0   Doorbell interrupts
> 
> The spurious interrupts are apparently from the virtio0-[input|output] devices.
> 

I was able to narrow it down to commit ecd10702baae5 ('KVM: PPC: Book3S HV: Handle pending exceptions on guest entry with MSR_EE')

Reverting the changes in this commit reduces the spurious interrupts
observed considerably. I'll try to root cause the issue and send a fix.

Thanks,
Gautam


      parent reply	other threads:[~2026-09-01  6:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14 14:56 [BUG] Continuously increasing spurious interrupts inside pSeries guest on PowerNV host Timothy Pearson
2026-08-14 15:14 ` Timothy Pearson
2026-08-17  4:02 ` Madhavan Srinivasan
2026-08-19  7:54 ` Gautam Menghani
2026-09-01  6:15 ` Gautam Menghani [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=apZteAd6mDv9URaD@Gautams-MacBook-Pro.local \
    --to=gautam@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=ritesh.list@gmail.com \
    --cc=tpearson@raptorengineering.com \
    /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