From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Timothy Pearson <tpearson@raptorengineering.com>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Ritesh Harjani <ritesh.list@gmail.com>
Subject: Re: [BUG] Interrupt timing warnings in pSeries guest on PowerNV host
Date: Thu, 27 Aug 2026 22:51:53 +0530 [thread overview]
Message-ID: <2086848f-f28f-42fc-80d4-e75af00fc9fc@linux.ibm.com> (raw)
In-Reply-To: <1435664226.21087.1787157496274.JavaMail.zimbra@raptorengineeringinc.com>
Hi Timothy,
On 8/21/26 10:08 PM, Timothy Pearson wrote:
> On a POWER9/PowerNV host, when running a pSeries guest using QEMU, sporadic interrupt timing warnings are observed. This is on kernel 6.12 (Debian Stable) on both host and guest, system load is moderate, the host CPUs are not pegged at 100% at any time. The guest has only one virtual CPU core assigned.
>
> [11622.031047] hrtimer: interrupt took 12354614 ns
> [46723.139964] hrtimer: interrupt took 8522695 ns
>
/*
* The next timer was already expired due to:
* - tracing
* - long lasting callbacks
* - being scheduled away when running in a VM
This message used to come if the timer expiry was in past and it was tried 3 times and still
can't catch up. Very likely it was due to guest being scheduled away.
This behavior has changed now and this particular trace has been removed.
https://lore.kernel.org/all/20260224163430.870639266@kernel.org/
> This *may* be related to the dropped / late interrupts I have reported in earlier messages, but it could also be a separate issue. QEMU version is 7.2.22.
prev parent reply other threads:[~2026-08-27 17:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 16:38 [BUG] Interrupt timing warnings in pSeries guest on PowerNV host Timothy Pearson
2026-08-27 17:21 ` Shrikanth Hegde [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=2086848f-f28f-42fc-80d4-e75af00fc9fc@linux.ibm.com \
--to=sshegde@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.