The "command mismatch" warning shouldn't be triggered by VIRTCHNL_OP_EVENT opcode, because the VIRTCHNL_OP_EVENT opcode is used by PF notifies status change events to VF. This patch fixed the issue.
Fixes: 837c2ed86e4c ("net/iavf: return error if opcode is mismatched") Cc: sta...@dpdk.org Signed-off-by: Junyu Jiang <junyux.ji...@intel.com> --- drivers/net/iavf/iavf_vchnl.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/drivers/net/iavf/iavf_vchnl.c b/drivers/net/iavf/iavf_vchnl.c index 33acea54a..331018f14 100644 --- a/drivers/net/iavf/iavf_vchnl.c +++ b/drivers/net/iavf/iavf_vchnl.c @@ -53,8 +53,11 @@ iavf_read_msg_from_pf(struct iavf_adapter *adapter, uint16_t buf_len, opcode, vf->cmd_retval); if (opcode != vf->pend_cmd) { - PMD_DRV_LOG(WARNING, "command mismatch, expect %u, get %u", - vf->pend_cmd, opcode); + if (opcode != VIRTCHNL_OP_EVENT) { + PMD_DRV_LOG(WARNING, + "command mismatch, expect %u, get %u", + vf->pend_cmd, opcode); + } return IAVF_ERR_OPCODE_MISMATCH; } -- 2.17.1