All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhu Lingshan <lingshan.zhu@intel.com>
To: jasowang@redhat.com, mst@redhat.com
Cc: virtualization@lists.linux-foundation.org,
	netdev@vger.kernel.org, kvm@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Zhu Lingshan <lingshan.zhu@intel.com>
Subject: [PATCH 2/2] vDPA/ifcvf: implement doorbell mapping for ifcvf
Date: Wed, 28 Apr 2021 16:21:33 +0800	[thread overview]
Message-ID: <20210428082133.6766-3-lingshan.zhu@intel.com> (raw)
In-Reply-To: <20210428082133.6766-1-lingshan.zhu@intel.com>

This commit implements doorbell mapping feature for ifcvf.
This feature maps the notify page to userspace, to eliminate
vmexit when kick a vq.

Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
---
 drivers/vdpa/ifcvf/ifcvf_main.c | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c b/drivers/vdpa/ifcvf/ifcvf_main.c
index e48e6b74fe2e..afcb71bc0f51 100644
--- a/drivers/vdpa/ifcvf/ifcvf_main.c
+++ b/drivers/vdpa/ifcvf/ifcvf_main.c
@@ -413,6 +413,23 @@ static int ifcvf_vdpa_get_vq_irq(struct vdpa_device *vdpa_dev,
 	return vf->vring[qid].irq;
 }
 
+static struct vdpa_notification_area ifcvf_get_vq_notification(struct vdpa_device *vdpa_dev,
+							       u16 idx)
+{
+	struct ifcvf_hw *vf = vdpa_to_vf(vdpa_dev);
+	struct vdpa_notification_area area;
+
+	if (vf->notify_pa % PAGE_SIZE) {
+		area.addr = 0;
+		area.size = 0;
+	} else {
+		area.addr = vf->notify_pa;
+		area.size = PAGE_SIZE;
+	}
+
+	return area;
+}
+
 /*
  * IFCVF currently does't have on-chip IOMMU, so not
  * implemented set_map()/dma_map()/dma_unmap()
@@ -440,6 +457,7 @@ static const struct vdpa_config_ops ifc_vdpa_ops = {
 	.get_config	= ifcvf_vdpa_get_config,
 	.set_config	= ifcvf_vdpa_set_config,
 	.set_config_cb  = ifcvf_vdpa_set_config_cb,
+	.get_vq_notification = ifcvf_get_vq_notification,
 };
 
 static int ifcvf_probe(struct pci_dev *pdev, const struct pci_device_id *id)
-- 
2.27.0


  parent reply	other threads:[~2021-04-28  8:27 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-28  8:21 [PATCH 0/2] vDPA/ifcvf: implement doorbell mapping feature Zhu Lingshan
2021-04-28  8:21 ` [PATCH 1/2] vDPA/ifcvf: record virtio notify base Zhu Lingshan
2021-04-28  8:39   ` Jason Wang
2021-04-28  8:39     ` Jason Wang
2021-04-28 10:00     ` Zhu, Lingshan
2021-04-28 10:09       ` Jason Wang
2021-04-28 10:09         ` Jason Wang
2021-04-28 10:18         ` Zhu, Lingshan
2021-04-28 11:48   ` kernel test robot
2021-04-28 11:48     ` kernel test robot
2021-04-28 11:48     ` kernel test robot
2021-04-28  8:21 ` Zhu Lingshan [this message]
2021-04-28  8:42   ` [PATCH 2/2] vDPA/ifcvf: implement doorbell mapping for ifcvf Jason Wang
2021-04-28  8:42     ` Jason Wang
2021-04-28  8:59     ` Zhu, Lingshan
2021-04-28  9:21       ` Jason Wang
2021-04-28  9:21         ` Jason Wang
2021-04-28  9:56         ` Zhu, Lingshan
2021-04-28 10:03           ` Jason Wang
2021-04-28 10:03             ` Jason Wang
2021-04-28 10:20             ` Zhu, Lingshan
2021-04-28 13:08               ` Jason Wang
2021-04-28 13:08                 ` Jason Wang
2021-04-29 11:26                 ` Zhu, Lingshan

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=20210428082133.6766-3-lingshan.zhu@intel.com \
    --to=lingshan.zhu@intel.com \
    --cc=jasowang@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.