From: Gordon Ross <gordon.w.ross@gmail.com>
To: illumos-developer <developer@lists.illumos.org>
Subject: Re: [developer] REVIEW: 14151 truss: truss should recognize VMM ioctl codes
Date: Tue, 12 Oct 2021 18:09:52 -0400 [thread overview]
Message-ID: <CAD0Ztp0swQTdX24zBCfNTySDKAteW1ALrJu+BHFLFonOEMeKFg@mail.gmail.com> (raw)
In-Reply-To: <65518007-D346-49BC-87B5-7E56CEE531C1@me.com>
Would be nice if (someday) truss didn't have to have every possible
ioctl in one big table, and might perhaps instead have a plug-in
framework like devfsadm to map ranges of ioctl codes to plug-ins that
know how to decode ioctl args for one device. One can dream anyway...
On Mon, Oct 11, 2021 at 11:31 AM Toomas Soome via illumos-developer
<developer@lists.illumos.org> wrote:
>
> hi!
>
> Please review: https://code.illumos.org/c/illumos-gate/+/1746
>
> thanks,
> toomas
> illumos / illumos-developer / see discussions + participants + delivery options Permalink
next prev parent reply other threads:[~2021-10-12 22:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 15:31 Toomas Soome
2021-10-12 22:09 ` Gordon Ross [this message]
2024-05-18 8:01 ` Toomas Soome
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=CAD0Ztp0swQTdX24zBCfNTySDKAteW1ALrJu+BHFLFonOEMeKFg@mail.gmail.com \
--to=gordon.w.ross@gmail.com \
--cc=developer@lists.illumos.org \
/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).