[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <326163fb-ed79-62ea-ed2d-cb3b7700db54@intel.com>
Date: Tue, 28 Jul 2020 09:37:25 -0700
From: Jacob Keller <jacob.e.keller@...el.com>
To: Moshe Shemesh <moshe@...lanox.com>,
"David S. Miller" <davem@...emloft.net>,
Jiri Pirko <jiri@...lanox.com>,
Vasundhara Volam <vasundhara-v.volam@...adcom.com>
Cc: netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH net-next RFC 00/13] Add devlink reload level option
On 7/27/2020 4:02 AM, Moshe Shemesh wrote:
> Introduce new option on devlink reload API to enable the user to select the
> reload level required. Complete support for all levels in mlx5.
> The following reload levels are supported:
> driver: Driver entities re-instantiation only.
So, this is the current support. Ok.
> fw_reset: Firmware reset and driver entities re-instantiation.
This would include firmware update? What about differing levels of
device/firmware reset? I.e. I think some of our HW has function level
reset, device wide reset, as well as EMP reset. For us, only EMP reset
would trigger firmware update.
> fw_live_patch: Firmware live patching only.
This is for update without reset, right?
Powered by blists - more mailing lists