From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: maddy@linux.ibm.com, linuxppc-dev@lists.ozlabs.org,
rostedt@goodmis.org, mhiramat@kernel.org
Cc: sshegde@linux.ibm.com, chleroy@kernel.org, riteshh@linux.ibm.com,
linux-kernel@vger.kernel.org, hbathini@linux.ibm.com
Subject: [PATCH 0/1] powerpc: Fix kuap warnings
Date: Fri, 9 Jan 2026 12:19:16 +0530 [thread overview]
Message-ID: <20260109064917.777587-1-sshegde@linux.ibm.com> (raw)
Recently stumbled upon these kuap warnings. This happens with
preempt=full/lazy kernel with function tracing enabled. What irked
me was kernel compilation was getting failed when i had tracing
enabled. It doesn't fail everytime. While running stress-ng memory class
it threw same warnings. So that helped to narrow it down.
So one possible way is to disable tracing for these enter/exit
vmx_usercopy. That seems to fix the bug/warnings. But that will make
them as non trace-able. If there is a better way to fix these warning while
keeping them as trace-able, please let me know.
Anyone with insights on amr, vmx and tracing, please advise.
Shrikanth Hegde (1):
powerpc: Fix kuap warnings on lazy/full preemption with tracing
arch/powerpc/kernel/process.c | 10 +++++-----
arch/powerpc/lib/vmx-helper.c | 4 ++--
2 files changed, 7 insertions(+), 7 deletions(-)
--
2.47.3
next reply other threads:[~2026-01-09 6:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-09 6:49 Shrikanth Hegde [this message]
2026-01-09 6:49 ` [PATCH 1/1] powerpc: Fix kuap warnings on lazy/full preemption with tracing Shrikanth Hegde
2026-01-09 8:11 ` [PATCH 0/1] powerpc: Fix kuap warnings Christophe Leroy (CS GROUP)
2026-01-09 12:19 ` Shrikanth Hegde
2026-01-09 12:54 ` Christophe Leroy (CS GROUP)
2026-01-26 13:54 ` Shrikanth Hegde
2026-02-17 9:31 ` Ritesh Harjani
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=20260109064917.777587-1-sshegde@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=hbathini@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=maddy@linux.ibm.com \
--cc=mhiramat@kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=rostedt@goodmis.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