[dtrace-discuss] Fwd: [osol-code] LOADABLE and LOADED syscalls

陶捷 TaoJie
Mon, 10 Sep 2007 13:40:47 -0000

---------- Forwarded message ----------
From: ?? TaoJie <eulertao at gmail.com>
Date: 2007-9-10 ??9:03
Subject: Re: [osol-code] LOADABLE and LOADED syscalls
To: James Carlson <james.d.carlson at sun.com>
Cc: opensolaris-code at opensolaris.org

thank you, James.

Then, in DTrace, loadable syscall modules are responsed by fbt provider, not
the syscall provider, aren''t they?


Regards,
TJ


2007/9/10, James Carlson <james.d.carlson at
sun.com>:
>
> ?? TaoJie writes:
> > in systm.h, there''s:
> > #define LOADABLE_SYSCALL(s) (s->sy_flags & SE_LOADABLE)
> >
> >
> > A syscall is LOADABLE if its sy_flags is set as SE_LOADABLE.
> > err... Then what does LOADABLE mean? What are the differences between
> normal
> > syscalls (e.g. read, write, exec) and LOADABLE syscalls ( e.g. syscall
> 67,
> > 68, 69)?
>
> Loadable syscalls have implementations in separate modules --
> generally located in /kernel/sys{,/$ISA} -- and named based on
> /etc/name_to_sysnum and with SYSENT_LOADABLE() in the sysent[] array.
> They get loaded into the kernel on demand.
>
> --
> James Carlson, Solaris Networking              <james.d.carlson at
sun.com>
> Sun Microsystems / 1 Network Drive         71.232W   Vox +1 781 442 2084
> MS UBUR02-212 / Burlington MA 01803-2757   42.496N   Fax +1 781 442 1677
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://mail.opensolaris.org/pipermail/dtrace-discuss/attachments/20070910/cdb92931/attachment.html>