public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Yoshinori Sato <ysato@users.sourceforge.jp>
Cc: linux-arch@vger.kernel.org
Subject: Re: [PATCH 13/16] h8300: ptrace helper
Date: Wed, 21 Jan 2015 09:51:34 +0100	[thread overview]
Message-ID: <2669606.8TdqsMIDS0@wuerfel> (raw)
In-Reply-To: <87h9vkvjnw.wl-ysato@users.sourceforge.jp>

On Wednesday 21 January 2015 13:31:47 Yoshinori Sato wrote:

> +long arch_ptrace(struct task_struct *child, long request,
> +		 unsigned long addr, unsigned long data)
> +{
> +	int ret;
> +	int regno = addr >> 2;
> +	unsigned long __user *datap = (unsigned long __user *) data;
> +
> +	switch (request) {
> +	/* read the word at location addr in the USER area. */
> +	case PTRACE_PEEKUSR: {
...
> +	case PTRACE_POKEUSR: /* write the word at location addr
...
> +	case PTRACE_GETREGS: { /* Get all gp regs from the child. */
...
> +	case PTRACE_SETREGS: { /* Set all gp regs in the child. */

For modern architecture implementations, we now use 'regset' to
abstract these, and simplify the arch_ptrace interface to
a single ptrace_request call. See openrisc or arm64 as examples.

	Arnd

  reply	other threads:[~2015-01-21  8:51 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1421813622.git.ysato@users.sourceforge.jp>
2015-01-21  4:23 ` [PATCH 01/16] h8300: Assembly headers Yoshinori Sato
2015-01-21 11:02   ` Geert Uytterhoeven
2015-01-21 17:22     ` Yoshinori Sato
2015-01-21  4:23 ` [PATCH 02/16] h8300: UAPI headers Yoshinori Sato
2015-01-21  8:46   ` Arnd Bergmann
2015-01-21 17:16     ` Yoshinori Sato
2015-01-21  4:24 ` [PATCH 03/16] h8300: defconfigs Yoshinori Sato
2015-01-21  8:47   ` Arnd Bergmann
2015-01-21  4:24 ` [PATCH 04/16] h8300: Memory management Yoshinori Sato
2015-01-21 10:57   ` Geert Uytterhoeven
2015-01-21 17:20     ` Yoshinori Sato
2015-01-21  4:25 ` [PATCH 05/16] h8300: Target depend (hw define) part Yoshinori Sato
2015-01-21  4:27 ` [PATCH 06/16] drivers: Add h8300 Yoshinori Sato
2015-01-21 11:03   ` Geert Uytterhoeven
2015-01-21 17:23     ` Yoshinori Sato
2015-01-21  4:29 ` [PATCH 07/16] Add ELF machine Yoshinori Sato
2015-01-21  4:29 ` [PATCH 08/16] h8300: Build scripts Yoshinori Sato
2015-01-21  4:30 ` [PATCH 09/16] h8300: kernel startup Yoshinori Sato
2015-01-21  4:30 ` [PATCH 10/16] h8300: Exception and Interrupt handler Yoshinori Sato
2015-01-21  4:31 ` [PATCH 11/16] h8300: Libraries Yoshinori Sato
2015-01-21  4:31 ` [PATCH 12/16] h8300: clocksource Yoshinori Sato
2015-01-21  8:49   ` Arnd Bergmann
2015-01-21 17:06     ` Yoshinori Sato
2015-01-21  4:31 ` [PATCH 13/16] h8300: ptrace helper Yoshinori Sato
2015-01-21  8:51   ` Arnd Bergmann [this message]
2015-01-21 17:08     ` Yoshinori Sato
2015-01-21  4:32 ` [PATCH 14/16] h8300: signal handler Yoshinori Sato
2015-01-21  4:32 ` [PATCH 15/16] h8300: system call entry table Yoshinori Sato
2015-01-21  4:32 ` [PATCH 16/16] h8300: misc functions Yoshinori Sato
2015-01-21  9:01   ` Arnd Bergmann
2015-01-21 17:19     ` Yoshinori Sato

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=2669606.8TdqsMIDS0@wuerfel \
    --to=arnd@arndb.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=ysato@users.sourceforge.jp \
    /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