From: David Miller <davem@davemloft.net>
To: hch@lst.de
Cc: hskinnemoen@atmel.com, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: missing kretprobes support on avr32 and sparc64
Date: Sat, 31 Mar 2007 12:00:23 -0700 (PDT) [thread overview]
Message-ID: <20070331.120023.91313972.davem@davemloft.net> (raw)
In-Reply-To: <20070331131522.GA15148@lst.de>
From: Christoph Hellwig <hch@lst.de>
Date: Sat, 31 Mar 2007 15:15:22 +0200
> Currently all avr32 and sparc64 don't support kretprobes unlike all
> other kprobes supporting architectures. This is not nice from the
> user interface point of view and from the ugly ifdefs point of view.
> Is there a reason these ports can't support kretprobes or was this
> simply an oversight / lazyness?
I just haven't gotten around to it yet.
Don't worry I'm aware of it. :-)
next prev parent reply other threads:[~2007-03-31 19:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-31 13:15 missing kretprobes support on avr32 and sparc64 Christoph Hellwig
2007-03-31 19:00 ` David Miller [this message]
2007-04-01 9:47 ` Håvard Skinnemoen
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=20070331.120023.91313972.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=hch@lst.de \
--cc=hskinnemoen@atmel.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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