system calls

system calls

[Rodrigo Ramos]

Hi,


I would like to know how many groups of system calls are there at Linux
2.4 and 2.6? Where can I find these informations in the Kernel?


Best Regards,
Rodrigo Ramos
www.triforsec.com.br

Re: system calls

[Robert Love]

On Sat, 2005-01-29 at 10:53 -0300, Rodrigo Ramos wrote:

> I would like to know how many groups of system calls are there at Linux
> 2.4 and 2.6? Where can I find these informations in the Kernel?

I don't know what you mean by groups (a nonempty set G with binary
operation * s.t. G is associativity, there exists e in G s.t. e*a=a*e=a,
and there exists i in G s.t. i*b=b*i=e?).

System calls are implemented per-architecture.  You can see the list at
the bottom of arch/i386/kernel/entry.S.  There is about 290.

System calls are prefixed by "sys_".  Thus, read(2) is implemented in
the kernel as sys_read().  It, for example, can be found in
fs/read_write.c.

Hope this helps.

	Robert Love

Re: system calls

[Andries Brouwer]

On Sat, Jan 29, 2005 at 12:47:38PM -0500, Robert Love wrote:

> System calls are prefixed by "sys_".  Thus, read(2) is implemented in
> the kernel as sys_read().

Now that you say this - of course you know that the actual
situation is much more messy. Sometimes I wonder whether
it would be useful to make such a statement more true
and for example change sys_olduname, sys_uname, sys_newuname
into sys_oldolduname, sys_olduname, sys_uname.

Andries

Re: system calls

[Rodrigo Ramos]

[-- Attachment #1: Type: text/plain, Size: 1099 bytes --]

Hi Robert,

Thank you very much for your help. It really helped me.
When a say groups a mean classes like File Structure, Process Related
and etc. But I already got what I needed... Once again Thank you very
much.

Best Regards,
Rodrigo Ramos
http://www.triforsec.com.br

On Sat, 2005-01-29 at 14:47, Robert Love wrote:
> On Sat, 2005-01-29 at 10:53 -0300, Rodrigo Ramos wrote:
> 
> > I would like to know how many groups of system calls are there at Linux
> > 2.4 and 2.6? Where can I find these informations in the Kernel?
> 
> I don't know what you mean by groups (a nonempty set G with binary
> operation * s.t. G is associativity, there exists e in G s.t. e*a=a*e=a,
> and there exists i in G s.t. i*b=b*i=e?).
> 
> System calls are implemented per-architecture.  You can see the list at
> the bottom of arch/i386/kernel/entry.S.  There is about 290.
> 
> System calls are prefixed by "sys_".  Thus, read(2) is implemented in
> the kernel as sys_read().  It, for example, can be found in
> fs/read_write.c.
> 
> Hope this helps.
> 
> 	Robert Love
> 
> 
> 
> 

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

system calls

[jaikumar Ganesh]

[-- Attachment #1.1: Type: text/plain, Size: 304 bytes --]

Hi
 I am pretty new to Xen and so any help would be appreciated.
  Say a user level process make a "write" system call on a VM running on
domain 1. Can anyone tell me the control flow (with the respect to the exact
functions that will called in Xen) to make this sytem call work?
 Thanks
Jaikumar

[-- Attachment #1.2: Type: text/html, Size: 417 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

Re: system calls

[Mark Williamson]

>  I am pretty new to Xen and so any help would be appreciated.
>   Say a user level process make a "write" system call on a VM running on
> domain 1. Can anyone tell me the control flow (with the respect to the
> exact functions that will called in Xen) to make this sytem call work?

The guest is allowed to install its own trap handler, so the write() system 
call invokes the normal syscall handler as in normal Linux.

The difference is only at the block device layer: instead of talking directly 
to a disk, the domU will queue IO requests in shared memory, which are then 
handled by the backend driver (usually in dom0).

There are no calls within Xen required to make write() itself work.  The block 
device driver will use grant tables and event channel calls in order to 
transfer the data.

Cheers,
Mark