From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29522 invoked by alias); 23 Aug 2012 02:23:08 -0000 Received: (qmail 29513 invoked by uid 22791); 23 Aug 2012 02:23:07 -0000 X-SWARE-Spam-Status: No, hits=-14.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD,USER_IN_DEF_DKIM_WL X-Spam-Check-By: sourceware.org Received: from ams-iport-3.cisco.com (HELO ams-iport-3.cisco.com) (144.254.224.146) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 23 Aug 2012 02:22:55 +0000 Received: from ams-core-4.cisco.com ([144.254.72.77]) by ams-iport-3.cisco.com with ESMTP; 23 Aug 2012 02:22:53 +0000 Received: from manesoni-ws.cisco.com ([10.65.79.7]) by ams-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id q7N2MpSw011742; Thu, 23 Aug 2012 02:22:52 GMT Received: by manesoni-ws.cisco.com (Postfix, from userid 1000) id 72E9360296; Thu, 23 Aug 2012 07:52:52 +0530 (IST) Date: Thu, 23 Aug 2012 02:23:00 -0000 From: Maneesh Soni To: Victor Kamensky Cc: systemtap@sourceware.org, Josh Stone , Per Hallsmark , Wade Farnsworth Subject: Re: What about MIPS support? Message-ID: <20120823022252.GA10067@cisco.com> Reply-To: manesoni@cisco.com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-IsSubscribed: yes Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org X-SW-Source: 2012-q3/txt/msg00237.txt.bz2 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