On Tue, 2004-11-16 at 15:14 -0600, Timur Tabi wrote: > Arjan van de Ven wrote: > > > once upon a time it was thought a needed evil to do system calls from > > kernel space... but now a nice workaround has been found (in 2.6) and > > it's no longer needed, so the evil hack is going away. > > What exactly is that work-around? > > I'm a little confused about making system calls from kernel space. ... via int 0x80 that was used for creating kernel threads, by calling int 0x80 for fork/clone. > Let's take sys_read() for example. Why can I just call sys_read() > directly from my module? depends which kernel you're talking about ;) In several 2.6's you can't. And you really really shouldn't... there's very few valid reasons to call sys_read, and I've yet to see one that applies to modules. -- -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
