From: Jiri Pirko <jiri@resnulli.us>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, idosch@mellanox.com, yotamg@mellanox.com,
eladr@mellanox.com, nogahf@mellanox.com, ogerlitz@mellanox.com,
ivecera@redhat.com, rostedt@goodmis.org, mingo@redhat.com,
jolsa@kernel.org
Subject: Re: [patch net-next 1/2] devlink: add hardware messages tracing facility
Date: Tue, 12 Jul 2016 08:44:48 +0200 [thread overview]
Message-ID: <20160712064448.GA1884@nanopsycho.orion> (raw)
In-Reply-To: <20160711.134516.2253721322702070372.davem@davemloft.net>
Mon, Jul 11, 2016 at 10:45:16PM CEST, davem@davemloft.net wrote:
>From: Jiri Pirko <jiri@resnulli.us>
>Date: Mon, 11 Jul 2016 15:18:47 +0200
>
>> From: Jiri Pirko <jiri@mellanox.com>
>>
>> Define a tracepoint and allow user to trace messages going to and from
>> hardware associated with devlink instance.
>>
>> Signed-off-by: Jiri Pirko <jiri@mellanox.com>
>
>Jiri, I don't think "having a devlink_ prefix" is a strong enough argument
>for doing things specially here.
>
>Just use the tracing facilities and export them the way everyone else
>does, and the way that two people already have suggested.
ok
next prev parent reply other threads:[~2016-07-12 6:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 13:18 [patch net-next 1/2] devlink: add hardware messages tracing facility Jiri Pirko
2016-07-11 13:18 ` [patch net-next 2/2] mlxsw: core: Trace EMAD messages Jiri Pirko
2016-07-11 15:01 ` [patch net-next 1/2] devlink: add hardware messages tracing facility David Ahern
2016-07-11 15:04 ` Jiri Pirko
2016-07-11 16:08 ` Steven Rostedt
2016-07-11 18:38 ` Jiri Pirko
2016-07-12 8:38 ` Jiri Pirko
2016-07-12 12:44 ` Steven Rostedt
2016-07-12 12:57 ` Jiri Pirko
2016-07-11 20:45 ` David Miller
2016-07-12 6:44 ` Jiri Pirko [this message]
2016-07-11 20:54 ` Steven Rostedt
2016-07-12 6:47 ` Jiri Pirko
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=20160712064448.GA1884@nanopsycho.orion \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=ivecera@redhat.com \
--cc=jolsa@kernel.org \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nogahf@mellanox.com \
--cc=ogerlitz@mellanox.com \
--cc=rostedt@goodmis.org \
--cc=yotamg@mellanox.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;
as well as URLs for NNTP newsgroup(s).