You're right that this probably is the cleanest solution.
However, this does not work for anything other than a debug parameter right? Suppose I want to communicate with the module, for something else. How can I do this? In Linux, drivers and modules can use the /proc filesystem to pass information from and to user space. A user can pass a parameter to the module by writing to such a virtual file in /proc. I understand that Solaris doesn't use /proc for that purpose, but is there maybe a similar mechanism for that? Thanks, Thomas On 5/21/07, Darren J Moffat <[EMAIL PROTECTED]> wrote:
Thomas De Schampheleire wrote: > Basically, I would like to be able to pass a debug_level parameter to > my module, that determines the amount of messages that will pass on > the console. If there is another way to achieve this, that is fine for > me as well. Rather than using console debugging it might be nicer to use DTrace static probes. Unless your module is used very early on it boot or where you may not otherwise have the ability to run dtrace(1M). Using DTrace static probes for debugging means you don't need to change a debug parameter just write a D program to get the probes to fire. -- Darren J Moffat
_______________________________________________ opensolaris-code mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
