Messages in this thread | | | Date | Sun, 12 Dec 1999 10:29:16 +0100 | From | Artur Skawina <> | Subject | Re: [patch] fastcall-2.3.32-B6, SYSENTER/SYSEXIT support |
| |
Richard Gooch wrote: > > I'm happy with the page mapping idea, but what concerns me is that we > can end up with a kernel which has a fair bit of code data embedded in > it, due to the increasing number of syscall instructions. Even if it's > contained in __init sections, it still bloats the kernel image. This > is a particular problem with embedded systems. Config options will > help here, but we have too many of those already.
hmm, i can't see this taking more that a few hundred bytes. it's not like every syscall would need a special entry point, and every one of them would be in a dozen versions. What was proposed so far wouldn't involve more than having a pair of very simple ("lea 4(%esp),%ebp;sysenter"-type) sequences, possibly in two or three versions, plus a small routine for really special cases (gettimeofday).
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |