From: William Cohen <wcohen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: eranian@hpl.hp.com, perfmon@napali.hpl.hp.com,
linux-ia64@vger.kernel.org, oprofile-list@lists.sourceforge.net,
perfctr-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [perfmon] 2.6.19 new perfmon code base + libpfm + pfmon
Date: Wed, 06 Dec 2006 21:39:15 +0000 [thread overview]
Message-ID: <45773883.5040003@redhat.com> (raw)
In-Reply-To: <20061205222810.GA6385@infradead.org>
Christoph Hellwig wrote:
> On Tue, Dec 05, 2006 at 12:24:36PM -0500, William Cohen wrote:
>
>>Some of the ptrace functions (e.g. ptrace_may_attach in perfmon_syscall.c)
>>being used in the perfmon kernel patches will go away with the utrace
>>patches: http://people.redhat.com/roland/utrace/
>
>
> At least for ptrace_may_attach that's not true in the lastest version
> from Roland - in fact it's the last unconditional function in ptrace.c
> in that version. I suggested to him to rename and move it in my review,
> though.
>
Sorry. I meant the function ptrace_check_attach(). -Will
WARNING: multiple messages have this Message-ID (diff)
From: William Cohen <wcohen@redhat.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: eranian@hpl.hp.com, perfmon@napali.hpl.hp.com,
linux-ia64@vger.kernel.org, oprofile-list@lists.sourceforge.net,
perfctr-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [perfmon] 2.6.19 new perfmon code base + libpfm + pfmon
Date: Wed, 06 Dec 2006 16:39:15 -0500 [thread overview]
Message-ID: <45773883.5040003@redhat.com> (raw)
In-Reply-To: <20061205222810.GA6385@infradead.org>
Christoph Hellwig wrote:
> On Tue, Dec 05, 2006 at 12:24:36PM -0500, William Cohen wrote:
>
>>Some of the ptrace functions (e.g. ptrace_may_attach in perfmon_syscall.c)
>>being used in the perfmon kernel patches will go away with the utrace
>>patches: http://people.redhat.com/roland/utrace/
>
>
> At least for ptrace_may_attach that's not true in the lastest version
> from Roland - in fact it's the last unconditional function in ptrace.c
> in that version. I suggested to him to rename and move it in my review,
> though.
>
Sorry. I meant the function ptrace_check_attach(). -Will
next prev parent reply other threads:[~2006-12-06 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 16:46 2.6.19 new perfmon code base + libpfm + pfmon Stephane Eranian
2006-12-04 16:46 ` Stephane Eranian
2006-12-05 17:24 ` [perfmon] " William Cohen
2006-12-05 17:24 ` William Cohen
2006-12-05 22:28 ` Christoph Hellwig
2006-12-05 22:28 ` Christoph Hellwig
2006-12-06 21:39 ` William Cohen [this message]
2006-12-06 21:39 ` William Cohen
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=45773883.5040003@redhat.com \
--to=wcohen@redhat.com \
--cc=eranian@hpl.hp.com \
--cc=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.