From: Roland McGrath <roland@redhat.com>
To: Grant Edwards <grant.b.edwards@gmail.com>
Cc: systemtap@sources.redhat.com
Subject: Re: Status of ARM user-space support?
Date: Tue, 26 Oct 2010 22:08:00 -0000 [thread overview]
Message-ID: <20101026220832.909BDC1EC2@blackie.sf.frob.com> (raw)
In-Reply-To: Grant Edwards's message of Tuesday, 26 October 2010 21:42:47 +0000 <ia7i0n$2f7$1@dough.gmane.org>
> > *** Update 4/24/09: arm work finished by Roland. (posted to
> > lkml?) Christoph pinged the mips maintainer, no reply seen.
>
> The arm work was posted upstream on 4/24, but there have been
> no replies from ARM folks. [...]
This refers to the work I did, which is only user_regset, tracehook, and
asm/syscall.h cleanups for ARM. None of that went in, though not for any
particular reason. Since then someone did something about asm/syscall.h
IIRC, but nobody has ever paid enough attention to merge the user_regset
and tracehook work I did. That stuff is internal kernel cleanups that
don't by itself give you any exciting new features (only some core-dump
support for the arcane register flavors that lacked them).
I have never done any work related to ARM support for instruction-copying
breakpoint insertion, which is the crux of kprobes and uprobes. I'm not
aware of what others may have done in those areas.
Thanks,
Roland
next prev parent reply other threads:[~2010-10-26 22:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 20:54 Grant Edwards
2010-10-26 21:27 ` Frank Ch. Eigler
2010-10-26 21:43 ` Grant Edwards
2010-10-26 22:08 ` Roland McGrath [this message]
2010-10-26 22:16 ` Grant Edwards
2010-10-27 2:28 ` Frank Ch. Eigler
2010-10-27 17:03 ` Jim Keniston
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=20101026220832.909BDC1EC2@blackie.sf.frob.com \
--to=roland@redhat.com \
--cc=grant.b.edwards@gmail.com \
--cc=systemtap@sources.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 read-only IMAP folder(s) and NNTP newsgroup(s).