From: Jason Gunthorpe <jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
To: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
linux-rdma <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: fprintf stderr in libibverbs
Date: Tue, 27 Oct 2009 23:42:32 -0600 [thread overview]
Message-ID: <20091028054232.GA1966@obsidianresearch.com> (raw)
Hi Roland,
I'd like to prepare a patch to do something with the fprintfs in
libibverbs src/init.c - but I'm not sure what you'd accept.
My main goal would be to remove prints from the library in common
cases like no IB drivers loaded, no devices present, or no
permissions. I have an app where the prints are inconvient.
What I was thinking was to return these cases via errno (ENOSYS,
ENODEV, EPERM) in ibv_get_device_list. Do you think that is OK?
Further, it would be nice to make the other prints work in some kind
of more general fashion so that the messages could be shown for GUI
apps, or what have you. The only thing I could think of was something
like:
int ibv_get_device_list_ex(struct ibv_device ***devices,int *num_devices,
const char **warning_msg);
Used as:
struct ibv_device **dev
int num_devices;
char *msg;
if ((rc = ibv_get_device_list_ex(&dev, &num, &msg))) {
errno = rc;
perror("Failed to get IB devices: '%s'",msg);
free(msg);
}
fputs(stderr,msg);
free(msg);
What do you think? Preference?
Thanks,
Jason
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2009-10-28 5:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 5:42 Jason Gunthorpe [this message]
[not found] ` <20091028054232.GA1966-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2009-10-28 17:51 ` fprintf stderr in libibverbs Roland Dreier
[not found] ` <adazl7bs8yt.fsf-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
2009-10-28 21:05 ` Jason Gunthorpe
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=20091028054232.GA1966@obsidianresearch.com \
--to=jgunthorpe-epgobjl8dl3ta4ec/59zmfatqe2ktcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.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