The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jorgen Hansen <jhansen@vmware.com>
To: linux-kernel@vger.kernel.org, virtualization@lists.linux-foundation.org
Cc: gregkh@linuxfoundation.org, pv-drivers@vmware.com,
	Jorgen Hansen <jhansen@vmware.com>,
	Vishnu Dasa <vdasa@vmware.com>
Subject: [PATCH v2 3/8] VMCI: dma dg: detect DMA datagram capability
Date: Thu,  3 Feb 2022 05:12:32 -0800	[thread overview]
Message-ID: <20220203131237.3380-4-jhansen@vmware.com> (raw)
In-Reply-To: <20220203131237.3380-1-jhansen@vmware.com>

Detect the VMCI DMA datagram capability, and if present, ack it
to the device.

Reviewed-by: Vishnu Dasa <vdasa@vmware.com>
Signed-off-by: Jorgen Hansen <jhansen@vmware.com>
---
 drivers/misc/vmw_vmci/vmci_guest.c | 11 +++++++++++
 include/linux/vmw_vmci_defs.h      |  1 +
 2 files changed, 12 insertions(+)

diff --git a/drivers/misc/vmw_vmci/vmci_guest.c b/drivers/misc/vmw_vmci/vmci_guest.c
index 38ee7ed32ab9..5a99d8e27873 100644
--- a/drivers/misc/vmw_vmci/vmci_guest.c
+++ b/drivers/misc/vmw_vmci/vmci_guest.c
@@ -565,6 +565,17 @@ static int vmci_guest_probe_device(struct pci_dev *pdev,
 		}
 	}
 
+	if (mmio_base != NULL) {
+		if (capabilities & VMCI_CAPS_DMA_DATAGRAM) {
+			caps_in_use |= VMCI_CAPS_DMA_DATAGRAM;
+		} else {
+			dev_err(&pdev->dev,
+				"Missing capability: VMCI_CAPS_DMA_DATAGRAM\n");
+			error = -ENXIO;
+			goto err_free_data_buffer;
+		}
+	}
+
 	dev_info(&pdev->dev, "Using capabilities 0x%x\n", caps_in_use);
 
 	/* Let the host know which capabilities we intend to use. */
diff --git a/include/linux/vmw_vmci_defs.h b/include/linux/vmw_vmci_defs.h
index 8fc00e2685cf..1ce2cffdc3ae 100644
--- a/include/linux/vmw_vmci_defs.h
+++ b/include/linux/vmw_vmci_defs.h
@@ -39,6 +39,7 @@
 #define VMCI_CAPS_DATAGRAM      BIT(2)
 #define VMCI_CAPS_NOTIFICATIONS BIT(3)
 #define VMCI_CAPS_PPN64         BIT(4)
+#define VMCI_CAPS_DMA_DATAGRAM  BIT(5)
 
 /* Interrupt Cause register bits. */
 #define VMCI_ICR_DATAGRAM      BIT(0)
-- 
2.25.1


  parent reply	other threads:[~2022-02-03 13:18 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 13:12 [PATCH v2 0/8] VMCI: dma dg: Add support for DMA datagrams Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 1/8] VMCI: dma dg: whitespace formatting change for vmci register defines Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 2/8] VMCI: dma dg: add MMIO access to registers Jorgen Hansen
2022-02-04 15:12   ` Greg KH
2022-02-07  8:51     ` Jorgen Hansen
2022-02-03 13:12 ` Jorgen Hansen [this message]
2022-02-03 13:12 ` [PATCH v2 4/8] VMCI: dma dg: set OS page size Jorgen Hansen
2022-02-04 15:12   ` Greg KH
2022-02-07  8:30     ` Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 5/8] VMCI: dma dg: register dummy IRQ handlers for DMA datagrams Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 6/8] VMCI: dma dg: allocate send and receive buffers " Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 7/8] VMCI: dma dg: add support for DMA datagrams sends Jorgen Hansen
2022-02-03 13:12 ` [PATCH v2 8/8] VMCI: dma dg: add support for DMA datagrams receive Jorgen Hansen

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=20220203131237.3380-4-jhansen@vmware.com \
    --to=jhansen@vmware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pv-drivers@vmware.com \
    --cc=vdasa@vmware.com \
    --cc=virtualization@lists.linux-foundation.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