From: Masami Hiramatsu <mhiramat@redhat.com>
To: "David J. Wilder" <dwilder@us.ibm.com>
Cc: systemtap@sourceware.org
Subject: Re: Arguments of inlines
Date: Mon, 05 Jan 2009 23:49:00 -0000 [thread overview]
Message-ID: <49629C9A.8080204@redhat.com> (raw)
In-Reply-To: <1231196411.10874.14.camel@wilder.ibm.com>
Hi,
David J. Wilder wrote:
> I am probing the following inline defined in include/rdma/ib_verbs.h:
>
> static inline int ib_post_send(struct ib_qp *qp,
> struct ib_send_wr *send_wr,
> struct ib_send_wr **bad_send_wr)
> {
> return qp->device->post_send(qp, send_wr, bad_send_wr);
> }
>
> And accessing the qp argument, however stap complains it can not
> reference $qp. It this a limitation? Any ideas?
I think this has been filed in bz1155
http://sources.redhat.com/bugzilla/show_bug.cgi?id=1155
Thanks,
--
Masami Hiramatsu
Software Engineer
Hitachi Computer Products (America) Inc.
Software Solutions Division
e-mail: mhiramat@redhat.com
prev parent reply other threads:[~2009-01-05 23:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 23:00 David J. Wilder
2009-01-05 23:14 ` Roland McGrath
2009-01-05 23:49 ` Masami Hiramatsu [this message]
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=49629C9A.8080204@redhat.com \
--to=mhiramat@redhat.com \
--cc=dwilder@us.ibm.com \
--cc=systemtap@sourceware.org \
/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).