El 1/1/26 a las 18:53, D. Ben Knoble escribió:
When emerging dev-util/perf (which picked up 6.14, latest stable), I got a warning about my kernel config:* Checking for suitable kernel configuration options ... * CONFIG_SCHED_OMIT_FRAME_POINTER: should not be set. But it is. * CONFIG_FRAME_POINTER: is not set when it should be. * Please check to make sure these options are set correctly. * Failure to do so may cause unexpected problems. I've had to adjust kernel settings a few times before for packages, but I normally find the relevant nodes to enable via the wiki for the package [1]. In this case, none are mentioned. There are quite a few config checks in the ebuild, though I can trace these specifically to cc02b6f4e4a3 (dev-util/perf: add 6.12, 2024-11-19) in the Gentoo repository. Anyway, I was curious about these checks since they're warnings, and after digging through the perf wiki, some bits of source code, etc., I can't figure out why these configs are relevant (or even where perf documents what it needs). Any tips? What might go wrong here? Or "ignore for now"? [1]: https://wiki.gentoo.org/wiki/Perf
The frame pointers are useful to debug. Some time ago (between 3'5" diskettes and systemd just being a nightmare not real...) we usually use one parameter -fomit-frame-pointer to compile gentoo...
Since Perf is supposed to help to know where things could go faster, is logic to suppose it would need to know what's happening, however, removing frame pointers usually did things faster xD
OpenPGP_0x57E64E0B7FC3BEDF.asc
Description: OpenPGP public key
OpenPGP_signature.asc
Description: OpenPGP digital signature
