Hi Breno, Thanks for explaining the rebase, rollout and debugging costs of carrying this out of tree. That's useful context from someone using the patchset.
CONFIG_EXPERT plus tainting on use could make experimental use more explicit. Those safeguards alone would not establish that firmware access, virtualization and runtime register updates are handled safely; the local restrictions still need validation against the hardware and firmware requirements. I'd like to hear Will's view on whether this opt-in approach could be acceptable in principle, and what requirements it would need to meet. I'm not planning to submit v3. Thanks, Koba
