linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Roland McGrath <roland@redhat.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] powerpc tracehook
Date: Sun, 27 Jul 2008 17:52:45 +1000	[thread overview]
Message-ID: <1217145165.11188.132.camel@pasglop> (raw)
In-Reply-To: <20080727064859.69692154280@magilla.localdomain>

On Sat, 2008-07-26 at 23:48 -0700, Roland McGrath wrote:
> These patches are posted for review, but you can just pull the GIT branch
> if you prefer.  Patch 1/5 corrects a long-standing (minor) error in ptrace
> behavior.  The others change no existing behavior, just enable new and
> future features to work on the arch.

Hi Roland !

Thanks for this. I haven't followed the story of tracehook so far, are
those patches dependent on something else or it's all already upstream
and do you think that's still 2.6.27 material ?

Cheers,
Ben.

> The following changes since commit 8be1a6d6c77ab4532e4476fdb8177030ef48b52c:
>   Linus Torvalds (1):
>         Merge branch 'for-linus' of git://git.kernel.org/.../roland/infiniband
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/frob/linux-2.6-utrace.git powerpc-tracehook
> 
> Roland McGrath (5):
>       powerpc: tracehook_signal_handler
>       powerpc: tracehook syscall
>       powerpc: tracehook: asm/syscall.h
>       powerpc: tracehook: TIF_NOTIFY_RESUME
>       powerpc: tracehook: CONFIG_HAVE_ARCH_TRACEHOOK
> 
>  arch/powerpc/Kconfig              |    1 +
>  arch/powerpc/kernel/entry_32.S    |   11 ++++-
>  arch/powerpc/kernel/entry_64.S    |   10 +++-
>  arch/powerpc/kernel/ptrace.c      |   47 ++++++++++-----------
>  arch/powerpc/kernel/signal.c      |   21 ++++++++-
>  include/asm-powerpc/ptrace.h      |    1 +
>  include/asm-powerpc/signal.h      |    3 +-
>  include/asm-powerpc/syscall.h     |   84 +++++++++++++++++++++++++++++++++++++
>  include/asm-powerpc/thread_info.h |    5 ++-
>  9 files changed, 147 insertions(+), 36 deletions(-)
>  create mode 100644 include/asm-powerpc/syscall.h
> 
> 
> Thanks,
> Roland
> --
> 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/

  parent reply	other threads:[~2008-07-27  7:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-27  6:48 [PATCH 0/5] powerpc tracehook Roland McGrath
2008-07-27  6:49 ` [PATCH 1/5] powerpc: tracehook_signal_handler Roland McGrath
2008-07-27  6:51 ` [PATCH 2/5] powerpc: tracehook syscall Roland McGrath
2008-07-27  6:51 ` [PATCH 3/5] powerpc: tracehook: asm/syscall.h Roland McGrath
2008-07-27  6:52 ` [PATCH 4/5] powerpc: tracehook: TIF_NOTIFY_RESUME Roland McGrath
2008-07-27  6:53 ` [PATCH 5/5] powerpc: tracehook: CONFIG_HAVE_ARCH_TRACEHOOK Roland McGrath
2008-07-27  7:52 ` Benjamin Herrenschmidt [this message]
2008-07-27  7:55   ` [PATCH 0/5] powerpc tracehook David Miller
2008-07-27  8:51     ` Benjamin Herrenschmidt

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=1217145165.11188.132.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.org \
    --cc=roland@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).