Subject: Re: IOCTL implementation and kernel/userland addresses
To: Frank van der Linden <fvdl@netbsd.org>
From: Bill Studenmund <wrstuden@netbsd.org>
List: tech-kern
Date: 02/07/2005 10:13:25
--hYooF8G/hrfVAmum
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Sat, Feb 05, 2005 at 01:12:39AM +0100, Frank van der Linden wrote:
> On Fri, Feb 04, 2005 at 03:57:44PM -0800, Bill Studenmund wrote:
> > Things like cache control, partition info, and wedge info are device
> > abstractions that every (appropriate) device should support, and that I
> > can see file systems and other kernel-level device users wanting to=20
> > access.
> >=20
> > So I think the best thing to do is to come up with a clean and sane way=
to=20
> > make all IOCTL use kernel-able and to document it. :-)
>=20
> Well.. you'd need an explicit kernel/userspace flag as far as I can see.
> Like uio does.
I think we can overload the proc parameter to handle this, and let proc =3D=
=3D=20
NULL indicate kernel context.
Take care,
Bill
--hYooF8G/hrfVAmum
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
iD8DBQFCB6/FWz+3JHUci9cRAsLlAJ4s/WLUrpvMCfZOT7KowfDsJzV4PgCfUuKb
gBbTTfoVcXQbxaQkCmBLhQo=
=l3Oo
-----END PGP SIGNATURE-----
--hYooF8G/hrfVAmum--