Re: [win-pv-devel] Debug print levels

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: win-pv-devel-bounces@xxxxxxxxxxxxxxxxxxxx [mailto:win-pv-devel-
> bounces@xxxxxxxxxxxxxxxxxxxx] On Behalf Of Rafal Wojdyla
> Sent: 14 July 2015 16:06
> To: win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> Subject: [win-pv-devel] Debug print levels
> 
> 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...

No, this is largely historic. It can be removed.

  Paul

> 
> --
> 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
_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel