From: Akhil Goyal

quoted

From: Akhil Goyal

quoted

quoted

From: Suanming Mou <redacted>

A keytag is a piece of data encrypted together with a DEK.

When a DEK is referenced by an MKEY.bsf through its index, the
keytag is also supplied in the BSF as plaintext. The HW will
decrypt the DEK (and the attached keytag) and will fail the
operation if the keytags don't match.

This commit adds the configuration of the keytag with devargs.

Signed-off-by: Suanming Mou <redacted>
Signed-off-by: Matan Azrad <redacted>
---

Documentation for devargs should be part of this patch.
Please split the last patch accordingly.

Title can be shortened to
Crypto/mlx5: add keytag devarg

Fix other patches of devargs accordingly.

As I said before, no devargs is really active before adding datapath patches.
The option to add all the supported features \ documentations in the
patch which actually adds the support is correct.

The last patch adds the capabilities and docs when all of them are
really supported.

In that case split the patches in such a manner that data path is added Before
devargs patch with some dummy values and add the devargs with
Appropriate documentation update in a later patch.

No, data-path must know all the devargs in advance, it cannot work well without them.