![]() | |||||||||||||
Messages in this thread |
> You knew this was coming... What's special about syscalls? There's the > r3 thing, but other than that... The whole codepath is a bit different, there's the syscall trace, we can avoid saving much more registers are syscalls are function calls and so can clobber the non volatiles, etc... > Thanks for your help with this stuff. As I've been slowly wrapping my > head around it I've been continuously wishing for some kind of design > rules document describing the various paths through the assembly code, > along with register conventions and such. I eventually did find the > conventions linked off the penguinppc website, but it was not obvious > from just reading the code or the ppc stuff in the Documentation directory. > > Chris -- Benjamin Herrenschmidt <benh@kernel.crashing.org> ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2005-03-22 13:02 [from the cache] ©2003-2008 | |||||||||||||