On Thu, Apr 28, 2005 at 11:10:53AM -0700, Chris Wright wrote:
> * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote:
> >
> > Split the i386 entry.S files into entry.S and syscall_table.S which
> > is included in the previous one (so actually there is no difference between
> > them) and use the syscall_table.S in the UML build, instead of tracking by
> > hand the syscall table changes (which is inherently error-prone).
>
> Xen can use this as well (it was on my todo list).
Maybe talking out of my ass here, but would it make sense to have the
generic syscalls in asm-generic, in the form of something like:
SYSCALL(__NR_getpid, sys_getpid)
?
The arch include this into its syscall table, would continue to define
__NR_*, and it would define SYSCALL (but all the syscall tables I've
seen are just arrays of pointers). This would allow the arches to
automatically get all the generic system calls, and they'd continue to
define on their own any arch-specific things.
Jeff
-------------------------------------------------------
SF.Net email is sponsored by: Tell us your software development plans!
Take this survey and enter to win a one-year sub to SourceForge.net
Plus IDC's 2005 look-ahead and a copy of this survey
Click here to start! http://www.idcswdc.com/cgi-bin/survey?id=105hix
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
