[win-pv-devel] Debug print levels

[RafaÅ WojdyÅa <omeg@xxxxxxxxxxxxxxxxxxxxxx>]

Is there a specific reason for the drivers force-unmasking all system
debug print levels on initialization (__DbgPrintEnable)? This overrides
any filter settings in the registry and makes debugging a bit annoying.
I'm using the highest level for some high-volume output and normally
want it disabled. Currently I can't configure that in the registry and
need to manually break in the debugger *after* PV drivers are loaded and
change the filter masks directly. I guess the issue is that IHVDRIVER id
is meant to be used by everyone...

-- 
RafaÅ WojdyÅa
Qubes Tools for Windows developer
https://www.qubes-os.org/

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel