From: Ingo Molnar <mingo@kernel.org>
To: Yafang Shao <laoar.shao@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: ardb@kernel.org, arnd@arndb.de, bp@alien8.de, dwmw@amazon.co.uk,
hpa@zytor.com, linux-kernel@vger.kernel.org,
michal.lkml@markovi.net, peterz@infradead.org,
tglx@linutronix.de, torvalds@linux-foundation.org,
vkuznets@redhat.com, yamada.masahiro@socionext.com
Subject: Re: [PATCH 13/15] x86/kconfig/64: Enable popular scheduler, cgroups and namespaces options in the defconfig
Date: Wed, 7 May 2025 09:06:04 +0200 [thread overview]
Message-ID: <aBsGXCKX8-2_Cn9x@gmail.com> (raw)
In-Reply-To: <9b31f1df-7dc6-468b-9418-0b13239df8bc@gmail.com>
* Yafang Shao <laoar.shao@gmail.com> wrote:
> Hello Mingo,
>
> > +CONFIG_VIRT_CPU_ACCOUNTING_GEN=y
> > +CONFIG_IRQ_TIME_ACCOUNTING=y
>
> Enabling CONFIG_IRQ_TIME_ACCOUNTING=y can lead to user-visible behavioral
> changes. For more context, please refer to the related discussion here:
> https://lore.kernel.org/all/20241222024734.63894-1-laoar.shao@gmail.com/ .
Yeah. I actually agree with your series. It (re-)includes IRQ/softirq
time in task CPU usage statistics even under IRQ_TIME_ACCOUNTING=y,
while still keeping the finegrained IRQ/softirq statistics as well,
correct?
The Kconfig option is also arguably rather misleading:
config IRQ_TIME_ACCOUNTING
bool "Fine granularity task level IRQ time accounting"
depends on HAVE_IRQ_TIME_ACCOUNTING && !VIRT_CPU_ACCOUNTING_NATIVE
help
Select this option to enable fine granularity task irq time
accounting. This is done by reading a timestamp on each
transitions between softirq and hardirq state, so there can be a
small performance impact.
It only warns about a small performance impact, but doesn't warn that
CPU accounting is changed in an incompatible fashion that surprises
tooling...
But I think we should probably treat this as a bug, not as lack of
documentation. Peter, do you concur?
> If we decide to enable it by default, we should clearly document this
> behavior change. Below is the patch I wrote earlier but haven’t sent
> out for review yet.
Note that it's not enabled by default - this patch is just about the
x86 defconfig.
Thanks,
Ingo
next prev parent reply other threads:[~2025-05-07 7:06 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 17:09 [PATCH -v2 00/15] x86/kconfig: Enable various kernel features in the defconfig, add the 'x86_32' subarchitecture build target and misc cleanups Ingo Molnar
2025-05-06 17:09 ` [PATCH 01/15] x86/kconfig/64: Refresh defconfig Ingo Molnar
2025-05-07 5:31 ` Arnd Bergmann
2025-05-07 6:22 ` Ingo Molnar
2025-05-06 17:09 ` [PATCH 02/15] x86/kconfig/32: " Ingo Molnar
2025-05-06 17:09 ` [PATCH 03/15] x86/kconfig: Rename x86_64_defconfig to defconfig.x86_64 and i386_defconfig to defconfig.i386 Ingo Molnar
2025-05-09 18:10 ` Arnd Bergmann
2025-05-15 13:16 ` Ingo Molnar
2025-05-06 17:09 ` [PATCH 04/15] x86/kbuild: Introduce the 'x86_32' subarchitecture Ingo Molnar
2025-05-07 5:44 ` Arnd Bergmann
2025-05-07 6:35 ` Ingo Molnar
2025-05-09 12:04 ` David Laight
2025-05-09 18:00 ` H. Peter Anvin
2025-05-09 18:05 ` Arnd Bergmann
2025-05-06 17:09 ` [PATCH 05/15] x86/kbuild: Remove ancient 'arch/i386/' and 'arch/x86_64/' directory removal 'archclean' target Ingo Molnar
2025-05-06 17:09 ` [PATCH 06/15] x86/tools: insn_decoder_test.c: Emit standard build success messages Ingo Molnar
2025-05-06 17:09 ` [PATCH 07/15] x86/tools: insn_sanity.c: " Ingo Molnar
2025-05-06 17:09 ` [PATCH 08/15] x86/kconfig/64: Enable the KVM host in the defconfig Ingo Molnar
2025-05-06 17:09 ` [PATCH 09/15] x86/kconfig/64: Enable more virtualization guest options in the defconfig: enable Xen, Xen_PVH, Jailhouse, ACRN, Intel TDX and Hyper-V Ingo Molnar
2025-05-08 9:21 ` Jürgen Groß
2025-05-15 13:19 ` Ingo Molnar
2025-05-06 17:09 ` [PATCH 10/15] x86/kconfig/64: Enable BPF support in the defconfig Ingo Molnar
2025-05-06 17:09 ` [PATCH 11/15] x86/kconfig/64: Enable popular MM options " Ingo Molnar
2025-05-06 17:09 ` [PATCH 12/15] x86/kconfig/64: Enable popular kernel debugging " Ingo Molnar
2025-05-06 17:09 ` [PATCH 13/15] x86/kconfig/64: Enable popular scheduler, cgroups and namespaces " Ingo Molnar
2025-05-07 3:00 ` Yafang Shao
2025-05-07 7:06 ` Ingo Molnar [this message]
2025-05-07 11:42 ` Yafang Shao
2025-05-07 16:22 ` Ingo Molnar
2025-05-08 5:56 ` Yafang Shao
2025-05-22 5:49 ` Yafang Shao
2025-05-07 5:11 ` Arnd Bergmann
2025-05-07 16:09 ` Ingo Molnar
2025-05-28 17:22 ` Michal Koutný
2025-05-06 17:09 ` [PATCH 14/15] x86/kconfig/64: Enable popular generic kernel " Ingo Molnar
2025-05-06 17:09 ` [PATCH 15/15] x86/kconfig/32: Synchronize the x86-32 defconfig to the x86-64 defconfig Ingo Molnar
2025-05-07 5:27 ` Arnd Bergmann
2025-05-07 17:41 ` Ingo Molnar
2025-05-07 17:55 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
2025-05-05 11:09 [PATCH 00/15] x86/kconfig: Enable various kernel features in the defconfig, add the 'x86_32' subarchitecture build target and misc cleanups Ingo Molnar
2025-05-05 11:09 ` [PATCH 13/15] x86/kconfig/64: Enable popular scheduler, cgroups and namespaces options in the defconfig Ingo Molnar
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=aBsGXCKX8-2_Cn9x@gmail.com \
--to=mingo@kernel.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=vkuznets@redhat.com \
--cc=yamada.masahiro@socionext.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
Powered by JetHome