From: Jacob Keller <jacob.e.keller@intel.com>
To: netdev@vger.kernel.org
Cc: Jonathan Corbet <corbet@lwn.net>,
intel-wired-lan@lists.osuosl.org,
David Ahern <dsahern@kernel.org>,
linux-doc@vger.kernel.org,
Stephen Hemminger <stephen@networkplumber.org>,
Eric Dumazet <edumazet@google.com>, Jiri Pirko <jiri@nvidia.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
"David S. Miller" <davem@davemloft.net>
Subject: [Intel-wired-lan] [net-next v2 0/2] devlink: implement dry run support for flash update
Date: Thu, 21 Jul 2022 14:14:45 -0700 [thread overview]
Message-ID: <20220721211451.2475600-1-jacob.e.keller@intel.com> (raw)
This is a re-send of the dry run support I submitted nearly a year ago at
https://lore.kernel.org/netdev/CO1PR11MB50898047B9C0FAA520505AFDD6B59@CO1PR11MB5089.namprd11.prod.outlook.com/
I had delayed sending this because of conflicting work in the ice driver at
the time, but then forgot about it and never got around to resubmitting it.
This adds a DEVLINK_ATTR_DRY_RUN which is used to indicate a request to
validate a potentially destructive operation without performing the actions
yet. In theory it could be used for other devlink operations in the future.
For flash update, it allows the user to validate a flash image, including
ensuring the driver for the device is willing to program it, without
actually committing an update yet.
There is an accompanying series for iproute2 which allows adding the dry-run
attribute. It does as Jakub suggested and checks the maximum attribute
before allowing the dry run in order to avoid accidentally performing a real
update on older kernels.
Changes since v1:
* Added maintainers to Cc (thanks for pointing out the script, Jiri!)
* Replaced bool in struct with u8 : 1
* Added kernel doc to devlink_flash_update_params
* Renamed PLDMFW parameter from dry_run to validate
* Reduced indentation in devlink.c by using nla_get_flag
Cc: Jacob Keller <jacob.e.keller@intel.com>
Cc: Jonathan Corbet <corbet@lwn.net>
Cc: Jiri Pirko <jiri@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>
Cc: Eric Dumazet <edumazet@google.com>
Cc: Jakub Kicinski <kuba@kernel.org>
Cc: Paolo Abeni <pabeni@redhat.com>
Cc: Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: David Ahern <dsahern@kernel.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>
Cc: linux-doc@vger.kernel.org
Cc: netdev@vger.kernel.org
Cc: intel-wired-lan@lists.osuosl.org
Jacob Keller (2):
devlink: add dry run attribute to flash update
ice: support dry run of a flash update to validate firmware file
Documentation/driver-api/pldmfw/index.rst | 10 ++++++++
.../networking/devlink/devlink-flash.rst | 23 +++++++++++++++++++
drivers/net/ethernet/intel/ice/ice_devlink.c | 3 ++-
.../net/ethernet/intel/ice/ice_fw_update.c | 14 +++++++----
include/linux/pldmfw.h | 5 ++++
include/net/devlink.h | 4 ++++
include/uapi/linux/devlink.h | 8 +++++++
lib/pldmfw/pldmfw.c | 12 ++++++++++
net/core/devlink.c | 17 +++++++++++++-
9 files changed, 90 insertions(+), 6 deletions(-)
base-commit: 5588d628027092e66195097bdf6835ddf64418b3
--
2.35.1.456.ga9c7032d4631
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next reply other threads:[~2022-07-21 21:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 21:14 Jacob Keller [this message]
2022-07-21 21:14 ` [Intel-wired-lan] [net-next v2 1/2] devlink: add dry run attribute to flash update Jacob Keller
2022-07-22 6:26 ` Jiri Pirko
2022-07-22 21:13 ` Keller, Jacob E
2022-07-21 21:14 ` [Intel-wired-lan] [net-next v2 2/2] ice: support dry run of a flash update to validate firmware file Jacob Keller
2022-07-21 21:14 ` [Intel-wired-lan] [iproute2-next v2 0/3] devlink: support dry run attribute for flash update Jacob Keller
2022-07-21 21:14 ` [Intel-wired-lan] [iproute2-next v2 1/3] update <linux/devlink.h> UAPI header Jacob Keller
2022-07-21 21:14 ` [Intel-wired-lan] [iproute2-next v2 2/3] mnlg: add function to get CTRL_ATTR_MAXATTR value Jacob Keller
2022-07-21 21:14 ` [Intel-wired-lan] [iproute2-next v2 3/3] devlink: add dry run attribute support to devlink flash Jacob Keller
2022-07-22 6:22 ` Jiri Pirko
2022-07-22 21:14 ` Keller, Jacob E
2022-07-21 23:52 ` [Intel-wired-lan] [net-next v2 0/2] devlink: implement dry run support for flash update Jakub Kicinski
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=20220721211451.2475600-1-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stephen@networkplumber.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