[Bug documentation/11224] setting module arguments needs to be tested/documented

[chwang at redhat dot com]

------- Additional Comments From chwang at redhat dot com  2010-02-03 16:30 -------
Created an attachment (id=4571)
 --> (http://sourceware.org/bugzilla/attachment.cgi?id=4571&action=view)
Sample stp file for modargs testing

Does very, very, very basic testing of modargs -- setting a number/string and
printing it.

WRT to the discussion about default values and overwriting them, I think it's
fine either way. But there should be an easy way to mark values as
'no-overwrite,' and it may be a good idea to make globals 'no-overwrite' by
default (to avoid accidental or intentional tampering with values)? I'm not
sure, but it seems like if we are going to make this feature optional it would
be safer as opt-in rather than opt-out.

Also, it would be nice from a user/scripting perspective if staprun one.ko
nonexistant_variable=a would run with a warning instead of terminating with an
error :)

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=11224

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.