Date: Wed, 09 Sep 1998 15:42:02 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Andrzej Bialecki <abial@nask.pl> Cc: freebsd-current@FreeBSD.ORG Subject: Re: Adding sysctl, part II Message-ID: <1492.905348522@critter.freebsd.dk> In-Reply-To: Your message of "Wed, 09 Sep 1998 14:54:22 %2B0200." <Pine.BSF.4.02A.9809091411140.21222-100000@korin.warman.org.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <Pine.BSF.4.02A.9809091411140.21222-100000@korin.warman.org.pl>, And
rzej Bialecki writes:
>On Wed, 9 Sep 1998, Poul-Henning Kamp wrote:
>
>>
>> >Well, I kind of figured out I probably need to use SYSCTL_PROC, and
>> >applied the following patch to machdep.c:
>>
>> Look at the
>> DDB_SHOW_COMMAND(msgbuf, db_show_msgbuf)
>> {
>>
>> at the bottom of kern/subr_prf.c
>
>Ah! I see it now - I should be glad it didn't explode in my face...
>
>It's still unclear to me, however, what should I do to retrieve not only
>the struct msgbuf (which the msgbufp points to), but the buffer itself as
>well. If I understand this correctly, once I retrieved the struct msgbuf
>contents, the msgbufp->msg_ptr is useless because it points to the data in
>kernel space, so I need to make another call to retrieve the buffer
>contents, right? The code in subr_prf.c can do this because it works in
>kernel space all the time, but I can't...
But you sysctl_proc does run in kernel, clone the code in from the
DDB_SHOW procedure...
--
Poul-Henning Kamp FreeBSD coreteam member
phk@FreeBSD.ORG "Real hackers run -current on their laptop."
"ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1492.905348522>