public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: David.Laight@ACULAB.COM (David Laight)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm: always update thread_info->syscall
Date: Tue, 27 Nov 2018 15:48:52 +0000	[thread overview]
Message-ID: <23ea6d5cbaac4cc3ad60d6184bbd1997@AcuMS.aculab.com> (raw)
In-Reply-To: <20181127153553.GE30658@n2100.armlinux.org.uk>

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)

  reply	other threads:[~2018-11-27 15:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-26 22:53 [PATCH] arm: always update thread_info->syscall Rafael David Tinoco
2018-11-26 23:33 ` Russell King - ARM Linux
2018-11-26 23:41   ` Russell King - ARM Linux
2018-11-26 23:44     ` Russell King - ARM Linux
2018-11-27 10:30       ` Rafael David Tinoco
2018-11-27 10:56         ` Russell King - ARM Linux
2018-11-27 15:35           ` Russell King - ARM Linux
2018-11-27 15:48             ` David Laight [this message]
2018-11-27 20:52             ` Rafael David Tinoco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23ea6d5cbaac4cc3ad60d6184bbd1997@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox