Date: Wed, 30 Dec 1998 23:24:53 -0700 From: Nate Williams <nate@mt.sri.com> To: Mike Smith <mike@smith.net.au> Cc: Nate Williams <nate@mt.sri.com>, Poul-Henning Kamp <phk@critter.freebsd.dk>, committers@FreeBSD.ORG Subject: Re: kvm_nlist emulation of n_type from kld symbol table at runtime. Message-ID: <199812310624.XAA07777@mt.sri.com> In-Reply-To: <199812310054.QAA00478@dingo.cdrom.com> References: <199812302359.QAA06821@mt.sri.com> <199812310054.QAA00478@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> > > >> Nutshell: Can anybody forsee the need to export symbol type to userland? > > > >> > > > >No, the obvious solution is to improve and expand the sysctl interface, > > > >which already provides size and type information. > > > > > > It would be trivial to implement in a sysctl, and we can even do it > > > as > > > sysctl kern.nlist.val.avenrun > > > sysctl kern.nlist.type.avenrun > > > if you want to... > > > > What about 'loadable' drivers that may have multiple symbols for > > multiple interfaces, ala network cards? > > > > kern.nlist.ed0.softc? > > Eugh. I think we're at cross purposes here. Exporting the kernel > symbol table for debugging purposes is one thing, exporting entities > out of the kernel for eg. statistical operations is another entirely. What about for things such as interrupt counts, collisions, and such. These aren't debugging issues, but do exist on a per-card basis. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199812310624.XAA07777>