automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Subject: [dpdk-test-report] |FAILURE| pw65675net/mlx5: fix xcapsulation validation
Date: 21 Feb 2020 14:35:14 -0800	[thread overview]
Message-ID: <ee68f5$9dh4fc@orsmga001.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2999 bytes --]

Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/65675

_apply issues_

Submitter: Matan Azrad <matan@mellanox.com>
Date: 2020-02-09 15:19:16
Reply_mail: 1581261556-10561-1-git-send-email-matan@mellanox.com
DPDK git baseline:
	Repo:dpdk-next-net-mlx, CommitID: 8c2e6036a173bc494fa8069e62d35fe3ff3f171f
	Repo:dpdk, CommitID: 41f24863e050810539f3a58ef901d23dddde0117

*Repo: dpdk-next-net-mlx
The HW doesn't support to do modify header action after ant
    encapsulation action.
    
    The split metadata function wrongly added the copy action in the end of
    the original actions list, hence, NIC egress flow with encapsulation
    action failed when the PMD worked with dv_xmeta_en mode.
    
    Move the copy action to be before and back to back with the
    encapsulation action for the aforementioned case.
    
    Fixes: 71e254bc0294 ("net/mlx5: split Rx flows to provide metadata copy")
--

	hairpin_flow = flow_check_hairpin_split(dev, attr, actions);
	if (hairpin_flow > 0) {
		if (hairpin_flow > MLX5_MAX_SPLIT_ACTIONS) {

error: patch failed: drivers/net/mlx5/mlx5_flow.c:4154
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
#define MLX5_FLOW_ACTION_DEC_TTL (1u << 19)
#define MLX5_FLOW_ACTION_SET_MAC_SRC (1u << 20)
--
#define MLX5_FLOW_ACTION_SET_IPV6_DSCP (1ull << 37)

#define MLX5_FLOW_FATE_ACTIONS \
	(MLX5_FLOW_ACTION_DROP | MLX5_FLOW_ACTION_QUEUE | \

error: patch failed: drivers/net/mlx5/mlx5_flow.h:186
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
 *   Holds the actions detected until now.
 * @param[in] action
--
 *   Pointer to flow attributes
 * @param[out] error
 *   Pointer to error structure.
 *

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:2140
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply
*Repo: dpdk
hairpin_flow = flow_check_hairpin_split(dev, attr, actions);
	if (hairpin_flow > 0) {
		if (hairpin_flow > MLX5_MAX_SPLIT_ACTIONS) {

error: patch failed: drivers/net/mlx5/mlx5_flow.c:4154
error: drivers/net/mlx5/mlx5_flow.c: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow.h...
error: while searching for:
#define MLX5_FLOW_ACTION_DEC_TTL (1u << 19)
#define MLX5_FLOW_ACTION_SET_MAC_SRC (1u << 20)
--
#define MLX5_FLOW_ACTION_SET_IPV6_DSCP (1ull << 37)

#define MLX5_FLOW_FATE_ACTIONS \
	(MLX5_FLOW_ACTION_DROP | MLX5_FLOW_ACTION_QUEUE | \

error: patch failed: drivers/net/mlx5/mlx5_flow.h:186
error: drivers/net/mlx5/mlx5_flow.h: patch does not apply
Checking patch drivers/net/mlx5/mlx5_flow_dv.c...
error: while searching for:
 *   Holds the actions detected until now.
 * @param[in] action
--
 *   Pointer to flow attributes
 * @param[out] error
 *   Pointer to error structure.
 *

error: patch failed: drivers/net/mlx5/mlx5_flow_dv.c:2140
error: drivers/net/mlx5/mlx5_flow_dv.c: patch does not apply

DPDK STV team

                 reply	other threads:[~2020-02-21 22:35 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='ee68f5$9dh4fc@orsmga001.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).