On 08.12.2022 10:36, Demi Marie Obenour wrote: > On Thu, Dec 08, 2022 at 09:02:57AM +0100, Jan Beulich wrote: >> Tainting the hypervisor in the event of finding an issue is certainly >> an option. > > I probably will not add such a mechanism, but if one exists I would be > happy to use it.
See common/kernel.c:add_taint(). What you would need to introduce is a new TAINT_* constant (and its associated handling), unless we wanted to reuse (abuse) an existing one (yet none looks to even come just close). Jan
