From: David Mosberger <davidm@napali.hpl.hp.com>
To: Keith Owens <kaos@ocs.com.au>
Cc: Rusty Lynch <rusty.lynch@intel.com>,
linux-ia64@vger.kernel.org,
Anil S Keshavamurthy <anil.s.keshavamurthy@intel.com>,
linux-kernel@vger.kernel.org, systemtap@sources.redhat.com,
Hien Nguyen <hien@us.ibm.com>
Subject: Re: [RFC] ia64 function return probes
Date: Fri, 03 Jun 2005 04:56:14 +0000 [thread overview]
Message-ID: <17055.58094.61614.587435@napali.hpl.hp.com> (raw)
In-Reply-To: <7459.1117765049@kao2.melbourne.sgi.com>
>>>>> On Fri, 03 Jun 2005 12:17:29 +1000, Keith Owens <kaos@ocs.com.au> said:
Keith> * arch_prepare_kretprobe() bumps sp by 16 bytes, to account
Keith> for the saved b0 and ar.pfs.
What if function arguments are being passed on the stack (e.g., more
than 8 scalar arguments)?
--david
next prev parent reply other threads:[~2005-06-03 4:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-01 21:39 [RFC] ia64 function return probes Rusty Lynch
2005-06-03 2:17 ` Keith Owens
2005-06-03 4:56 ` David Mosberger [this message]
2005-06-03 18:01 ` Lynch, Rusty
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=17055.58094.61614.587435@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=anil.s.keshavamurthy@intel.com \
--cc=hien@us.ibm.com \
--cc=kaos@ocs.com.au \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty.lynch@intel.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