From: Alex Williamson <alex.williamson@redhat.com>
To: Vivek Kasireddy <vivek.kasireddy@intel.com>
Cc: dongwon.kim@intel.com, virtualization@lists.linux-foundation.org
Subject: Re: [RFC 3/3] vfio: Share the KVM instance with Vdmabuf
Date: Tue, 19 Jan 2021 08:39:55 -0700 [thread overview]
Message-ID: <20210119083955.1cc9eae3@omen.home.shazbot.org> (raw)
In-Reply-To: <20210119082812.822291-4-vivek.kasireddy@intel.com>
On Tue, 19 Jan 2021 00:28:12 -0800
Vivek Kasireddy <vivek.kasireddy@intel.com> wrote:
> Getting a copy of the KVM instance is necessary for mapping Guest
> pages in the Host.
>
> TODO: Instead of invoking the symbol directly, there needs to be a
> better way of getting a copy of the KVM instance probably by using
> other notifiers. However, currently, KVM shares its instance only
> with VFIO and therefore we are compelled to bind the passthrough'd
> device to vfio-pci.
Yeah, this is a bad solution, sorry, vfio is not going to gratuitously
call out to vhost to share a kvm pointer. I'd prefer to get rid of
vfio having any knowledge or visibility of the kvm pointer. Thanks,
Alex
> Signed-off-by: Vivek Kasireddy <vivek.kasireddy@intel.com>
> ---
> drivers/vfio/vfio.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/vfio/vfio.c b/drivers/vfio/vfio.c
> index 4ad8a35667a7..9fb11b1ad3cd 100644
> --- a/drivers/vfio/vfio.c
> +++ b/drivers/vfio/vfio.c
> @@ -2213,11 +2213,20 @@ static int vfio_unregister_iommu_notifier(struct vfio_group *group,
> return ret;
> }
>
> +extern void vhost_vdmabuf_get_kvm(unsigned long action, void *data);
> void vfio_group_set_kvm(struct vfio_group *group, struct kvm *kvm)
> {
> + void (*fn)(unsigned long, void *);
> +
> group->kvm = kvm;
> blocking_notifier_call_chain(&group->notifier,
> VFIO_GROUP_NOTIFY_SET_KVM, kvm);
> +
> + fn = symbol_get(vhost_vdmabuf_get_kvm);
> + if (fn) {
> + fn(VFIO_GROUP_NOTIFY_SET_KVM, kvm);
> + symbol_put(vhost_vdmabuf_get_kvm);
> + }
> }
> EXPORT_SYMBOL_GPL(vfio_group_set_kvm);
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-01-19 15:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-19 8:28 [RFC 0/3] Introduce Vdmabuf driver Vivek Kasireddy
2021-01-19 8:28 ` [RFC 1/3] virtio: " Vivek Kasireddy
2021-01-19 8:28 ` [RFC 2/3] vhost: Add Vdmabuf backend Vivek Kasireddy
2021-01-19 8:28 ` [RFC 3/3] vfio: Share the KVM instance with Vdmabuf Vivek Kasireddy
2021-01-19 15:39 ` Alex Williamson [this message]
2021-01-20 0:14 ` Kasireddy, Vivek
2021-01-20 0:50 ` Alex Williamson
2021-01-20 3:05 ` Tian, Kevin
2021-01-20 3:36 ` Alex Williamson
2021-01-21 3:15 ` Kasireddy, Vivek
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=20210119083955.1cc9eae3@omen.home.shazbot.org \
--to=alex.williamson@redhat.com \
--cc=dongwon.kim@intel.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=vivek.kasireddy@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).