From: Maneesh Soni <manesoni@cisco.com>
To: Victor Kamensky <kamensky@cisco.com>
Cc: systemtap@sourceware.org, Josh Stone <jistone@redhat.com>,
Per Hallsmark <Per.Hallsmark@windriver.com>,
Wade Farnsworth <wade_farnsworth@mentor.com>
Subject: Re: What about MIPS support?
Date: Thu, 23 Aug 2012 02:23:00 -0000 [thread overview]
Message-ID: <20120823022252.GA10067@cisco.com> (raw)
In-Reply-To: <Pine.GSO.4.64.1208221222170.28511@infra-view11.cisco.com>
On Wed, Aug 22, 2012 at 01:04:12PM -0700, Victor Kamensky wrote:
....
> Wrt of MIPS kprobes, it should be there already, somewhere in latest
> kernel. Most of support was there for a while. Maneesh and I
> contributed patch that let probe be inserted into jump instructions
> (that was limitation of original implementation, which we quickly
> discovered when we used for real cases). We worked on top 2.6.32
> kernel. As understand there is current gradual departure from
> uprobes .. so our mips uprobes part may need rework a bit.
^^^^^^ I guess you meant utrace?
>
Actually the current (as in mainline kernel) approach for uprobes
is not using utrace, so there could be almost a re-write effort.
Thanks
Maneesh
next prev parent reply other threads:[~2012-08-23 2:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-22 20:04 Victor Kamensky
2012-08-23 2:23 ` Maneesh Soni [this message]
2012-08-23 14:33 ` Ananth N Mavinakayanahalli
2012-08-23 22:11 ` Josh Stone
2012-10-15 21:21 ` Victor Kamensky
2012-10-23 23:43 ` Josh Stone
2015-08-05 12:42 ` William Cohen
[not found] ` <CAJdmCr+1s6JLW3DsGxbdqPcpnD1+wNo5VwAifm6UN-SWE+PKmw@mail.gmail.com>
2015-08-05 16:25 ` William Cohen
[not found] ` <CAJdmCrLN3w6J3XHTCx0uMDQDAc6LB+5qC3o7Rr+KABAriwNATg@mail.gmail.com>
2015-08-06 1:30 ` William Cohen
2015-08-06 13:04 ` William Cohen
-- strict thread matches above, loose matches on Subject: below --
2012-08-17 16:33 Hallsmark, Per
2012-08-18 2:20 ` Josh Stone
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=20120823022252.GA10067@cisco.com \
--to=manesoni@cisco.com \
--cc=Per.Hallsmark@windriver.com \
--cc=jistone@redhat.com \
--cc=kamensky@cisco.com \
--cc=systemtap@sourceware.org \
--cc=wade_farnsworth@mentor.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).