public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ananth N Mavinakayanahalli <ananth@in.ibm.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Alexey Dobriyan <adobriyan@gmail.com>,
	Andi Kleen <andi@firstfloor.org>,
	Christoph Hellwig <hch@infradead.org>,
	"Frank Ch. Eigler" <fche@redhat.com>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Roland McGrath <roland@redhat.com>,
	linux-kernel@vger.kernel.org, utrace-devel@redhat.com
Subject: Re: [PATCH 6/7] implement utrace-ptrace
Date: Mon, 21 Dec 2009 19:20:43 +0530	[thread overview]
Message-ID: <20091221135043.GC12670@in.ibm.com> (raw)
In-Reply-To: <20091221134837.GB12670@in.ibm.com>

On Mon, Dec 21, 2009 at 07:18:37PM +0530, Ananth N Mavinakayanahalli wrote:
> On Fri, Dec 18, 2009 at 02:11:40AM +0100, Oleg Nesterov wrote:
> > The patch adds the new file, kernel/ptrace-utrace.c, which contains
> > the new implementation of ptrace over utrace.
> > 
> > This file is not compiled until we have CONFIG_UTRACE option, will be
> > added by the next "utrace core" patch.
> > 
> > It's supposed to be an invisible implementation change, nothing should
> > change to userland when CONFIG_UTRACE is enabled.
> > 
> > Signed-off-by: Roland McGrath <roland@redhat.com>
> > Signed-off-by: Oleg Nesterov <oleg@redhat.com>
> > ---
> 
> Oleg,
> 
> ptrace/utrace performs better with the ptrace-tests [1] testsuite (1 failure
> vs. 3 with vanilla ptrace [1]). The gdb testsuite also has no
> regressions. In fact, the results on the gdb testsuite are identical.

Forgot to mention the tests were on powerpc.

      reply	other threads:[~2009-12-21 13:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-18  1:11 [PATCH 6/7] implement utrace-ptrace Oleg Nesterov
2009-12-21 13:48 ` Ananth N Mavinakayanahalli
2009-12-21 13:50   ` Ananth N Mavinakayanahalli [this message]

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=20091221135043.GC12670@in.ibm.com \
    --to=ananth@in.ibm.com \
    --cc=adobriyan@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fche@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=roland@redhat.com \
    --cc=utrace-devel@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