From: SL Baur <steve@kbuxd.necst.nec.co.jp>
To: Shaya Potter <spotter@cs.columbia.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: figuring out which ioctl's a system needs?
Date: Thu, 14 Nov 2002 17:40:35 +0900 [thread overview]
Message-ID: <15827.24963.123936.782801@sofia.bsd2.kbnes.nec.co.jp> (raw)
> 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.
next reply other threads:[~2002-11-14 8:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 8:40 SL Baur [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-13 22:53 figuring out which ioctl's a system needs? Shaya Potter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15827.24963.123936.782801@sofia.bsd2.kbnes.nec.co.jp \
--to=steve@kbuxd.necst.nec.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=spotter@cs.columbia.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).