From mboxrd@z Thu Jan 1 00:00:00 1970 Received: with ECARTIS (v1.0.0; list linux-mips); Thu, 22 Oct 2009 20:34:50 +0200 (CEST) Received: from mail-bw0-f221.google.com ([209.85.218.221]:52311 "EHLO mail-bw0-f221.google.com" rhost-flags-OK-OK-OK-OK) by ftp.linux-mips.org with ESMTP id S1493439AbZJVSeo (ORCPT ); Thu, 22 Oct 2009 20:34:44 +0200 Received: by bwz21 with SMTP id 21so611187bwz.24 for ; Thu, 22 Oct 2009 11:34:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:from:reply-to:to:cc :in-reply-to:references:content-type:organization:date:message-id :mime-version:x-mailer:content-transfer-encoding; bh=IJWIMlzK4jNJqND3HWrCDh5OPZ4dszyAAYwRp28ukaE=; b=ff9tQeekREb2bHJD0gAFCWhyJxdxhqhtT7YLvMi5YlWFKt1O+8CPwjVgRyWRTFQ+Dl e6qVZ29yCUpaIvl7lWTfB2CAd82kRtcR0C2qQtkPh2nb2zCW2Iq7JnI5jnHWUXcuVizi w4iixkmONCILq59XdyGGMaxTFtwhiXfbZA458= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:from:reply-to:to:cc:in-reply-to:references:content-type :organization:date:message-id:mime-version:x-mailer :content-transfer-encoding; b=cqtKytet/LF5v3JaLbDCFq/aDE5YLaDVeIIg7uigKZSG72jLirmRlUiP8PqCTmg+Lp EVecVi/A8DVJhBiWhvHJQ8qtKWJkJ5JWo7jT0/8pOGFUNviLNp2eAVy7aoJAa0scG7+j v86yibQKeZrsPP2qST1AwOsmGPFsWwxTusSmI= Received: by 10.204.2.211 with SMTP id 19mr3337283bkk.6.1256236478034; Thu, 22 Oct 2009 11:34:38 -0700 (PDT) Received: from ?172.16.2.101? ([222.92.8.142]) by mx.google.com with ESMTPS id 21sm2400213fks.39.2009.10.22.11.34.33 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 22 Oct 2009 11:34:37 -0700 (PDT) Subject: Re: [PATCH -v4 4/9] tracing: add static function tracer support for MIPS From: Wu Zhangjin Reply-To: wuzhangjin@gmail.com To: rostedt@goodmis.org Cc: linux-kernel@vger.kernel.org, linux-mips@linux-mips.org, Thomas Gleixner , Ralf Baechle , Nicholas Mc Guire In-Reply-To: <1256234361.20866.796.camel@gandalf.stny.rr.com> References: <028867b99ec532b84963a35e7d552becc783cafc.1256135456.git.wuzhangjin@gmail.com> <2f73eae542c47ac5bbb9f7280e6c0271d193e90d.1256135456.git.wuzhangjin@gmail.com> <3f0d3515f74a58f4cfd11e61b62a129fdc21e3a7.1256135456.git.wuzhangjin@gmail.com> <1256138686.18347.3039.camel@gandalf.stny.rr.com> <1256233679.23653.7.camel@falcon> <1256234361.20866.796.camel@gandalf.stny.rr.com> Content-Type: text/plain Organization: DSLab, Lanzhou University, China Date: Fri, 23 Oct 2009 02:34:29 +0800 Message-Id: <1256236469.23653.12.camel@falcon> Mime-Version: 1.0 X-Mailer: Evolution 2.26.1 Content-Transfer-Encoding: 7bit Return-Path: X-Envelope-To: <"|/home/ecartis/ecartis -s linux-mips"> (uid 0) X-Orcpt: rfc822;linux-mips@linux-mips.org Original-Recipient: rfc822;linux-mips@linux-mips.org X-archive-position: 24451 X-ecartis-version: Ecartis v1.0.0 Sender: linux-mips-bounce@linux-mips.org Errors-to: linux-mips-bounce@linux-mips.org X-original-sender: wuzhangjin@gmail.com Precedence: bulk X-list: linux-mips On Thu, 2009-10-22 at 13:59 -0400, Steven Rostedt wrote: > On Fri, 2009-10-23 at 01:47 +0800, Wu Zhangjin wrote: > > On Wed, 2009-10-21 at 11:24 -0400, Steven Rostedt wrote: > > > > Is t0 and t1 safe for mcount to use? Remember, mcount does not follow > > > the dynamics of C function ABI. > > > > So, perhaps we can use the saved registers(a0,a1...) instead. > > I don't know. I was just asking. I just used a0,a1,a2 instead of t0,t1,t2, we are safe to use them for they have been saved/restored. Thanks!