[C/R ARM][PATCH 1/3] ARM: Rudimentary syscall interfaces
Matt Helsley
matthltc at us.ibm.com
Tue Mar 23 22:03:42 EDT 2010
On Tue, Mar 23, 2010 at 08:53:42PM +0000, Russell King - ARM Linux wrote:
> On Sun, Mar 21, 2010 at 09:06:03PM -0400, Christoffer Dall wrote:
> > This small commit introduces a global state of system calls for ARM
> > making it possible for a debugger or checkpointing to gain information
> > about another process' state with respect to system calls.
>
> I don't particularly like the idea that we always store the syscall
> number to memory for every system call, whether the stored version is
> used or not.
>
> Since ARM caches are generally not write allocate, this means mostly
> write-only variables can have a higher than expected expense.
>
> Is there not some thread flag which can be checked to see if we need to
> store the syscall number?
Perhaps before we freeze the task we can save the syscall number on ARM.
The patches suggest that the signal delivery path -- which the freezer
utilizes -- has the syscall number already.
Should work since the threads must be frozen first anyway.
Cheers,
-Matt Helsley
More information about the linux-arm-kernel
mailing list