mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier.adi@gmail.com>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Roland McGrath <roland@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: ptracee data structures cleanup
Date: Wed, 22 Apr 2009 19:01:51 -0400	[thread overview]
Message-ID: <8bd0f97a0904221601t110b0dd4xfe1f957de0e3fff7@mail.gmail.com> (raw)
In-Reply-To: <20090422220400.GA22755@redhat.com>

On Wed, Apr 22, 2009 at 18:04, Oleg Nesterov wrote:
> On 04/21, Roland McGrath wrote:
>> [We have been on fine details here that are quite purely ptrace innards for
>> a while now.  I think discussion at this level of detail about this stuff
>> quite far from utrace per se belongs on LKML.]
>
> Agreed. s/utrace-devel/lkml/.
>
>> > > The clean-up should get rid of PT_DTRACE entirely.
>> >
>> > Agreed. But this needs another patch...
>>
>> Yes, or several.  It always gets fiddly when to get lots of little arch
>> changes merged.  The 90% that are just one-liner removal of wholly unused
>> PT_DTRACE can probably go in as a single patch to Linus instead of tiny
>> ones through each arch tree.
>
> OK. I'd like to finally do at least something. Please look at the 4 patches
> attached.
>
> Unfortunately, I know nothing about these arches, so I can only rely on grep.
> But it really looks like nobody except arch/um actually uses DTRACE.
>
> There are also some strange defines in blackfin and m68k, PF_DTRACE_BIT and
> PT_DTRACE_BIT, which seems to be unused too. At least I failed to find
> anything related in asm. Perhaps I should learn how to cross compile.

Blackfin was based on m68knommu, so it is most likely unused by us.
the only ptrace consumers are gdb(server) and strace and neither use
it afaik.
-mike

  parent reply	other threads:[~2009-04-22 23:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20090330185146.D525AFC3AB@magilla.sf.frob.com>
     [not found] ` <20090408203954.GA26816@redhat.com>
     [not found]   ` <20090416204004.GA28013@redhat.com>
     [not found]     ` <20090416232430.4DAE4FC3C6@magilla.sf.frob.com>
     [not found]       ` <20090420183718.GC32527@redhat.com>
     [not found]         ` <20090421011354.4B19EFC3C7@magilla.sf.frob.com>
     [not found]           ` <20090421214819.GA22845@redhat.com>
     [not found]             ` <20090422032205.B8D39FC3C7@magilla.sf.frob.com>
2009-04-22 22:04               ` Oleg Nesterov
2009-04-22 22:06                 ` remove PT_DTRACE from arch/* except arch/um Oleg Nesterov
2009-04-23  6:36                   ` Roland McGrath
2009-04-22 22:17                 ` PT_DTRACE && uml Oleg Nesterov
2009-04-23  6:39                   ` Roland McGrath
2009-04-23 16:02                   ` Jeff Dike
2009-04-26 22:09                     ` Oleg Nesterov
2009-04-26 23:18                       ` copy_process() && ti->flags (Was: PT_DTRACE && uml) Oleg Nesterov
2009-04-27  2:10                         ` Roland McGrath
2009-04-22 23:01                 ` Mike Frysinger [this message]
2009-04-23  6:41                   ` ptracee data structures cleanup Roland McGrath

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=8bd0f97a0904221601t110b0dd4xfe1f957de0e3fff7@mail.gmail.com \
    --to=vapier.adi@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --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

all inboxes | Powered by JetHome®