From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Aboorva Devarajan <aboorvad@linux.ibm.com>
Cc: Christophe Leroy <chleroy@kernel.org>,
linux-kernel@vger.kernel.org,
Ritesh Harjani <ritesh.list@gmail.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
linuxppc-dev@lists.ozlabs.org,
Mukesh Kumar Chaurasiya <mchauras@linux.ibm.com>
Subject: Re: [PATCH] powerpc/entry: Fix double accounting of user time on interrupt entry
Date: Wed, 2 Sep 2026 12:37:43 +0530 [thread overview]
Message-ID: <95913fca-5631-40ff-abed-4afad99722e6@linux.ibm.com> (raw)
In-Reply-To: <20260902050628.2553909-1-aboorvad@linux.ibm.com>
Hi Aboorva.
On 9/2/26 10:36 AM, Aboorva Devarajan wrote:
> Since the switch to generic entry, an interrupt taken from user mode
> accounts user time twice: once in arch_interrupt_enter_prepare() and
> again in arch_enter_from_user_mode(), which irqentry_enter() invokes
> for the same interrupt:
>
> arch_interrupt_enter_prepare()
> account_cpu_user_entry()
> irqentry_enter()
> arch_enter_from_user_mode()
> account_cpu_user_entry()
>
> account_cpu_user_entry() accumulates the time spent in user mode
> since the last return to user space, so the second call charges the
> same interval again.
>
> With CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y this roughly doubles the
> reported user time of any workload that takes interrupts. On a
> pseries LPAR, ps/top show ~200% CPU for a single-threaded CPU-bound
> loop, and time(1) reports user time about twice the elapsed time.
>
Could you please run mpstat with 50% or less loading workload like stress-ng
and document the difference in changelog.
> Remove the accounting from arch_interrupt_enter_prepare() and rely on
> arch_enter_from_user_mode(), which runs for both syscalls and
> interrupts. The duplicate account_stolen_time() call is removed the
> same way.
>
> Fixes: bee25f97ad24 ("powerpc: Enable GENERIC_ENTRY feature")
> Signed-off-by: Aboorva Devarajan <aboorvad@linux.ibm.com>
> ---
> Verified on a pseries LPAR (CONFIG_VIRT_CPU_ACCOUNTING_NATIVE=y),
Usual default is VIRT_CPU_ACCOUNTING_GEN, selected by NO_HZ_FULL.
Most distros usually enable NO_HZ_FULL=y.
At hindsight, I don't see the issue dependency on it. But better to be sure.
> 7.3.0-rc1, single-threaded CPU-bound loop:
>
> Before:
>
> $ python3 -c 'while True: pass' &
> $ sleep 3; ps -p $! -o pid,etime,time,pcpu
> PID ELAPSED TIME %CPU
> 4980 00:03 00:00:06 210
>
> After:
>
> $ python3 -c 'while True: pass' &
> $ sleep 3; ps -p $! -o pid,etime,time,pcpu
> PID ELAPSED TIME %CPU
> 4951 00:03 00:00:03 105
>
> arch/powerpc/include/asm/entry-common.h | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/entry-common.h b/arch/powerpc/include/asm/entry-common.h
> index c5adb5006361..984294e62568 100644
> --- a/arch/powerpc/include/asm/entry-common.h
> +++ b/arch/powerpc/include/asm/entry-common.h
> @@ -222,8 +222,6 @@ static inline void arch_interrupt_enter_prepare(struct pt_regs *regs)
>
> if (user_mode(regs)) {
> kuap_lock();
> - account_cpu_user_entry();
> - account_stolen_time();
> } else {
> kuap_save_and_lock(regs);
> /*
> @@ -426,6 +424,10 @@ static __always_inline void arch_enter_from_user_mode(struct pt_regs *regs)
> #endif
> kuap_assert_locked();
> booke_restore_dbcr0();
> + /*
> + * User and stolen time is accounted here for every entry from
> + * user mode. The interrupt prepare hooks must not account again.
> + */
> account_cpu_user_entry();
> account_stolen_time();
>
>
> base-commit: fb442a6673ff1046bf67754957d95880fdb394b5
next prev parent reply other threads:[~2026-09-02 7:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 5:06 Aboorva Devarajan
2026-09-02 5:31 ` Mukesh Kumar Chaurasiya
2026-09-02 17:45 ` Aboorva Devarajan
2026-09-02 5:36 ` Christophe Leroy (CS GROUP)
2026-09-02 19:44 ` Aboorva Devarajan
2026-09-03 4:51 ` Christophe Leroy (CS GROUP)
2026-09-02 7:07 ` Shrikanth Hegde [this message]
2026-09-02 20:14 ` Aboorva Devarajan
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=95913fca-5631-40ff-abed-4afad99722e6@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=aboorvad@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mchauras@linux.ibm.com \
--cc=ritesh.list@gmail.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
all inboxes | Powered by JetHome®