From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Lingyu Liu <lingyu.liu@intel.com>, <intel-wired-lan@lists.osuosl.org>
Cc: kevin.tian@intel.com, yi.l.liu@intel.com,
phani.r.burra@intel.com, Xu Ting <ting.xu@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next V1 01/15] ice: Fix missing legacy 32byte RXDID in the supported bitmap
Date: Tue, 20 Jun 2023 13:05:38 +0200 [thread overview]
Message-ID: <85ae556e-4038-2618-c8be-7ca035daa024@intel.com> (raw)
In-Reply-To: <20230620100001.5331-2-lingyu.liu@intel.com>
On 6/20/23 11:59, Lingyu Liu wrote:
> From: Xu Ting <ting.xu@intel.com>
>
> 32byte legacy descriptor format is preassigned.
> Commit e753df8fbca5 ("ice: Add support Flex RXD") created a
> supported RXDIDs bitmap according to DDP package. But it missed
> the legacy 32byte RXDID since it is not listed in the package.
> This patch adds this RXDID to the bitmap.
Please reword into imperative mood, perhaps staring with "Mark 32byte
legacy descriptor format as supported int the supported RXDIDs flags",
or similar.
>
> Signed-off-by: Xu Ting <ting.xu@intel.com>
> Signed-off-by: Lingyu Liu <lingyu.liu@intel.com>
> ---
> drivers/net/ethernet/intel/ice/ice_virtchnl.c | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/ice/ice_virtchnl.c b/drivers/net/ethernet/intel/ice/ice_virtchnl.c
> index 92490fe655ea..ae1e09f0875b 100644
> --- a/drivers/net/ethernet/intel/ice/ice_virtchnl.c
> +++ b/drivers/net/ethernet/intel/ice/ice_virtchnl.c
> @@ -2615,12 +2615,14 @@ static int ice_vc_query_rxdid(struct ice_vf *vf)
> goto err;
> }
>
> - /* Read flexiflag registers to determine whether the
> - * corresponding RXDID is configured and supported or not.
This part of the comment was valuable too (esp given all the bit
twiddling in the loop). Perhaps you could bring it back?
> - * Since Legacy 16byte descriptor format is not supported,
> - * start from Legacy 32byte descriptor.
> + /* RXDIDs supported by DDP package can be read from the register
> + * to get the supported RXDID bitmap. But the legacy 32byte RXDID
> + * is not listed in DDP package, add it in the bitmap manually.
I had to grep defines of ICE_RXDID_FLEX_NIC and ICE_RXDID_LEGACY_1 to
ensure that the code is correct (it is), comment above has certainly
helped me. Perhaps you could add "(and skip check for it in the loop)"
at the end of the above sentence (after "manually")?
> + * Legacy 16byte descriptor is not supported.
> */
> - for (i = ICE_RXDID_LEGACY_1; i < ICE_FLEX_DESC_RXDID_MAX_NUM; i++) {
> + rxdid->supported_rxdids |= BIT(ICE_RXDID_LEGACY_1);
> +
> + for (i = ICE_RXDID_FLEX_NIC; i < ICE_FLEX_DESC_RXDID_MAX_NUM; i++) {
> regval = rd32(hw, GLFLXP_RXDID_FLAGS(i, 0));
> if ((regval >> GLFLXP_RXDID_FLAGS_FLEXIFLAG_4N_S)
> & GLFLXP_RXDID_FLAGS_FLEXIFLAG_4N_M)
Codewise it's ok!
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
next prev parent reply other threads:[~2023-06-20 11:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 9:59 [Intel-wired-lan] [PATCH iwl-next V1 00/15] Add E800 live migration driver Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 01/15] ice: Fix missing legacy 32byte RXDID in the supported bitmap Lingyu Liu
2023-06-20 11:05 ` Przemek Kitszel [this message]
2023-06-21 9:16 ` Liu, Lingyu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 02/15] ice: add function to get rxq context Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 03/15] ice: check VF migration status before sending messages to VF Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 04/15] ice: add migration init field and helper functions Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 05/15] ice: save VF messages as device state Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 06/15] ice: save and restore " Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 07/15] ice: do not notify VF link state during migration Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 08/15] ice: change VSI id in virtual channel message after migration Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 09/15] ice: save and restore RX queue head Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 10/15] ice: save and restore TX " Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 11/15] ice: stop device before saving device states Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 12/15] ice: mask VF advanced capabilities if live migration is activated Lingyu Liu
2023-06-20 9:59 ` [Intel-wired-lan] [PATCH iwl-next V1 13/15] vfio/ice: implement vfio_pci driver for E800 devices Lingyu Liu
2023-06-20 10:00 ` [Intel-wired-lan] [PATCH iwl-next V1 14/15] vfio: Expose vfio_device_has_container() Lingyu Liu
2023-06-20 10:00 ` [Intel-wired-lan] [PATCH iwl-next V1 15/15] vfio/ice: support iommufd vfio compat mode Lingyu Liu
2023-06-20 11:08 ` [Intel-wired-lan] [PATCH iwl-next V1 00/15] Add E800 live migration driver Paul Menzel
2023-06-27 9:06 ` Liu, Lingyu
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=85ae556e-4038-2618-c8be-7ca035daa024@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=kevin.tian@intel.com \
--cc=lingyu.liu@intel.com \
--cc=phani.r.burra@intel.com \
--cc=ting.xu@intel.com \
--cc=yi.l.liu@intel.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