kvmmmu tracing

Johannes Berg
2009-11-23T11:06:14Z

[-- Attachment #1: Type: text/plain, Size: 577 bytes --]

Commit f691fe1da7e2715137d21ae5a80bec64db4625db is really broken wrt.
the userspace interface for tracing because of the weird
KVM_MMU_PAGE_PRINTK macro.

Maybe we should have a "unsafe for export" flag for events, if they do
strange things like that?

As it stands, I can't use trace-cmd on an x86 machine that has kvm
enabled because it will try to read all the kvm stuff. Arguably, it
should only try to parse it when it needs it (i.e. not for me) but still
it's very inconvenient to export something to userspace that it cannot
possibly understand.