* figuring out which ioctl's a system needs?
@ 2002-11-13 22:53 Shaya Potter
0 siblings, 0 replies; 2+ messages in thread
From: Shaya Potter @ 2002-11-13 22:53 UTC (permalink / raw)
To: linux-kernel
I'm trying to figure out what is the subset of ioctl's a system needs to
run. I figure the best way is sticking a printk in sys_ioctl, and
having it printk the number, so that syslog can pick it up, and then go
through the list. This way I can use the system normally for a week to
collect the information I need.
Is there an easier way, or is there a way that I can make my life easier
(i.e. going from printk'd number to header file include).
thanks,
shaya potter
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: figuring out which ioctl's a system needs?
@ 2002-11-14 8:40 SL Baur
0 siblings, 0 replies; 2+ messages in thread
From: SL Baur @ 2002-11-14 8:40 UTC (permalink / raw)
To: Shaya Potter; +Cc: linux-kernel
> I'm trying to figure out what is the subset of ioctl's a system needs
> to run. I figure the best way is sticking a printk in sys_ioctl, and
> having it printk the number, so that syslog can pick it up, and then
> go through the list. This way I can use the system normally for a
> week to collect the information I need.
> Is there an easier way, or is there a way that I can make my life
> easier (i.e. going from printk'd number to header file include).
Install the Linux Trace Toolkit and enable tracing for ioctls.
See http://www.opersys.com/LTT for details.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-11-14 8:31 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-11-13 22:53 figuring out which ioctl's a system needs? Shaya Potter
2002-11-14 8:40 SL Baur
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).