From: Johannes Berg <johannes@sipsolutions.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
Alex Vesker <valex@mellanox.com>
Cc: netdev@vger.kernel.org, jiri@mellanox.com, dsahern@gmail.com,
andrew@lunn.ch, rahul.lakkireddy@chelsio.com,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH net-next v2 00/11] devlink: Add support for region access
Date: Wed, 15 Aug 2018 22:25:28 +0200 [thread overview]
Message-ID: <1534364728.3547.46.camel@sipsolutions.net> (raw)
In-Reply-To: <20180711114821.1d50ba63@cakuba.lan> (sfid-20180711_204833_719898_307A4DC2)
On Wed, 2018-07-11 at 11:48 -0700, Jakub Kicinski wrote:
> CC: linux-wireless, wifi chips used to have similar problem
>
> On Wed, 11 Jul 2018 13:42:57 +0300, Alex Vesker wrote:
> > This is a proposal which will allow access to driver defined address
> > regions using devlink. Each device can create its supported address
> > regions and register them. A device which exposes a region will allow
> > access to it using devlink.
We usually just implement it for debug dumping, and use devcoredump for
that. How does this overlap? Some of the devcoredump data may be
"synthetic" in the sense that it doesn't really have to be strictly a
device memory region, so it's not quite the same, but what's the
intended use case for this?
johannes
prev parent reply other threads:[~2018-08-15 23:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1531305788-29420-1-git-send-email-valex@mellanox.com>
2018-07-11 18:48 ` [PATCH net-next v2 00/11] devlink: Add support for region access Jakub Kicinski
2018-07-12 6:21 ` Alex Vesker
2018-08-15 20:25 ` Johannes Berg [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=1534364728.3547.46.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=andrew@lunn.ch \
--cc=dsahern@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=jiri@mellanox.com \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rahul.lakkireddy@chelsio.com \
--cc=valex@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).