Re: Proposed change to makesyscalls.sh

[Martin Husemann <martin%duskware.de@localhost>]

On Sun, Aug 05, 2018 at 06:24:25AM +0800, Paul Goyette wrote:
> The primary usage for this is for arch/usermode's syscallemu() which
> (according to those working on arch/usermode) could be considered
> "dangerous" and "should never be autoloaded.  Having this change will
> allow use of a "registered" syscall number rather than having to have
> a work-around for PR kern/45781.

Doesn't (say) 211 work? Then just mark it as reserved in syscalls.master
in a comment, like:

;
; Syscalls 210-219 are reserved for dynamically loaded syscalls
;
210     EXTERN  MODULAR openafs { int|sys||afssys(long id, long a1, long a2, \
                          long a3, long a4, long a5, long a6); }
211     UNIMPL	/* syscallemu for sys/arch/usermode/modules/syscallemu */
212     UNIMPL
213     UNIMPL
214     UNIMPL

Has anyone analyzed PR 45781? Is it just about extending the valid range
or does it break for this numbers too?

Martin