[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23ea6d5cbaac4cc3ad60d6184bbd1997@AcuMS.aculab.com>
Date: Tue, 27 Nov 2018 15:48:52 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Russell King - ARM Linux' <linux@...linux.org.uk>,
Rafael David Tinoco <rafael.tinoco@...aro.org>
CC: Vladimir Murzin <vladimir.murzin@....com>,
Vincent Whitchurch <vincent.whitchurch@...s.com>,
Nick Desaulniers <ndesaulniers@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"stable@...r.kernel.org" <stable@...r.kernel.org>,
Masahiro Yamada <yamada.masahiro@...ionext.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
Thomas Gleixner <tglx@...utronix.de>,
Timothy E Baldwin <T.E.Baldwin99@...bers.leeds.ac.uk>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: RE: [PATCH] arm: always update thread_info->syscall
From: Russell King - ARM Linux
> Sent: 27 November 2018 15:36
...
> There appears to be no documentation at all of this interface, so there
> is no definition of how it is supposed to work or what it is supposed
> to expose beyond what little information is in the original patch:
>
> http://lkml.iu.edu/hypermail/linux/kernel/0807.2/0577.html
>
> This adds /proc/PID/syscall and /proc/PID/task/TID/syscall magic files.
> These use task_current_syscall() to show the task's current system call
> number and argument registers, stack pointer and PC. For a task blocked
> but not in a syscall, the file shows "-1" in place of the syscall number,
> followed by only the SP and PC. For a task that's not blocked, it shows
> "running".
I 'like' the way the columns for sp and pc jump about ...
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists