---------- Forwarded message ----------
From: 陶捷 TaoJie <[EMAIL PROTECTED]>
Date: 2007-9-10 下午9:03
Subject: Re: [osol-code] LOADABLE and LOADED syscalls
To: James Carlson <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
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 <[EMAIL PROTECTED]>:
>
> 陶捷 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 <[EMAIL PROTECTED]>
> 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
>
_______________________________________________
dtrace-discuss mailing list
[email protected]
