On Wed, Oct 14, 2026 at 02:17:45PM +0800, Koba Ko wrote: > For controlled performance characterization, is there an existing kernel > mechanism or a different design you would recommend? Or do you think these > experimental controls are better kept out of tree?
As a user of this patchset, I am trying hard to avoid carrying it out of tree, either as patches or as a driver. Out-of-tree code makes kernel rebases and rollouts slower, and debugging more complex. Is there a way to keep a generic interface available under CONFIG_EXPERT, or something similar, so that users who want to experiment can use it? We could even taint the kernel when the interface is used, to make it clear that the user is messing with things they should not (!?). Thanks, --breno
