DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sean Morrissey <sean.morrissey@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>,
	Kevin Laatz <kevin.laatz@intel.com>
Cc: dev@dpdk.org, Sean Morrissey <sean.morrissey@intel.com>
Subject: [PATCH v1] dma/idxd: add completion status for page fault
Date: Tue, 23 Aug 2022 14:47:00 +0000	[thread overview]
Message-ID: <20220823144700.718995-1-sean.morrissey@intel.com> (raw)

Add a status for page faults to be used when getting the
completion status of an operation.

Signed-off-by: Sean Morrissey <sean.morrissey@intel.com>
---
 drivers/dma/idxd/idxd_common.c  | 2 ++
 drivers/dma/idxd/idxd_hw_defs.h | 1 +
 2 files changed, 3 insertions(+)

diff --git a/drivers/dma/idxd/idxd_common.c b/drivers/dma/idxd/idxd_common.c
index c77200a457..6fe8ad4884 100644
--- a/drivers/dma/idxd/idxd_common.c
+++ b/drivers/dma/idxd/idxd_common.c
@@ -169,6 +169,8 @@ get_comp_status(struct idxd_completion *c)
 	case IDXD_COMP_STATUS_INCOMPLETE:
 	case IDXD_COMP_STATUS_SUCCESS:
 		return RTE_DMA_STATUS_SUCCESSFUL;
+	case IDXD_COMP_STATUS_PAGE_FAULT:
+		return RTE_DMA_STATUS_PAGE_FAULT;
 	case IDXD_COMP_STATUS_INVALID_OPCODE:
 		return RTE_DMA_STATUS_INVALID_OPCODE;
 	case IDXD_COMP_STATUS_INVALID_SIZE:
diff --git a/drivers/dma/idxd/idxd_hw_defs.h b/drivers/dma/idxd/idxd_hw_defs.h
index 2a219c1312..a38540f283 100644
--- a/drivers/dma/idxd/idxd_hw_defs.h
+++ b/drivers/dma/idxd/idxd_hw_defs.h
@@ -48,6 +48,7 @@ struct idxd_hw_desc {
 
 #define IDXD_COMP_STATUS_INCOMPLETE        0
 #define IDXD_COMP_STATUS_SUCCESS           1
+#define IDXD_COMP_STATUS_PAGE_FAULT     0X03
 #define IDXD_COMP_STATUS_INVALID_OPCODE 0x10
 #define IDXD_COMP_STATUS_INVALID_SIZE   0x13
 #define IDXD_COMP_STATUS_SKIPPED        0xFF /* not official IDXD error, needed as placeholder */
-- 
2.34.1


             reply	other threads:[~2022-08-23 14:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-23 14:47 Sean Morrissey [this message]
2022-10-03 17:34 ` Thomas Monjalon

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=20220823144700.718995-1-sean.morrissey@intel.com \
    --to=sean.morrissey@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=kevin.laatz@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;
as well as URLs for NNTP newsgroup(s).