iommu.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: joro@8bytes.org, will@kernel.org, robin.murphy@arm.com,
	eric.auger@redhat.com, virtualization@lists.linux-foundation.org,
	iommu@lists.linux.dev, akihiko.odaki@daynix.com
Subject: Re: [PATCH] iommu/virtio: Detach domain on endpoint release
Date: Wed, 17 May 2023 13:20:51 -0300	[thread overview]
Message-ID: <ZGT+44a6RYZ999kz@nvidia.com> (raw)
In-Reply-To: <20230510081157.GA3326511@myrica>

On Wed, May 10, 2023 at 09:11:57AM +0100, Jean-Philippe Brucker wrote:

> > diff --git a/drivers/iommu/virtio-iommu.c b/drivers/iommu/virtio-iommu.c
> > index 5b8fe9bfa9a5..3d3d4462359e 100644
> > --- a/drivers/iommu/virtio-iommu.c
> > +++ b/drivers/iommu/virtio-iommu.c
> > @@ -788,6 +788,28 @@ static int viommu_attach_dev(struct iommu_domain *domain, struct device *dev)
> >  	return 0;
> >  }
> >  
> > +static void viommu_detach_dev(struct viommu_endpoint *vdev)
> > +{
> > +	int i;
> > +	struct virtio_iommu_req_detach req;
> > +	struct viommu_domain *vdomain = vdev->vdomain;
> > +	struct iommu_fwspec *fwspec = dev_iommu_fwspec_get(vdev->dev);
> > +
> > +	if (!vdomain)
> > +		return;
> > +
> > +	req = (struct virtio_iommu_req_detach) {
> > +		.head.type	= VIRTIO_IOMMU_T_DETACH,
> > +		.domain		= cpu_to_le32(vdomain->id),
> > +	};
> > +
> > +	for (i = 0; i < fwspec->num_ids; i++) {
> > +		req.endpoint = cpu_to_le32(fwspec->ids[i]);
> > +		WARN_ON(viommu_send_req_sync(vdev->viommu, &req, sizeof(req)));
> > +	}
> > +	vdev->vdomain = NULL;

Not for this patch, but something to work on..

I assume detach disconnects the container on the VFIO side and puts it
into a BLOCKED state?

Can you wrapper this into a BLOCKED domain like we are moving drivers
toward, and then attach the blocked domain instead of introducing this
special case?

I've been thinking about having some core code support to do fairly
common pattern of 'parking' the iommu at some well defined translation
mode, BLOCKED in this case.

Thanks,
Jason

  reply	other threads:[~2023-05-17 16:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-14 15:07 [PATCH] iommu/virtio: Detach domain on endpoint release Jean-Philippe Brucker
2023-04-20  1:20 ` Akihiko Odaki
2023-05-10  8:11 ` Jean-Philippe Brucker
2023-05-17 16:20   ` Jason Gunthorpe [this message]
2023-05-18 13:56     ` Jean-Philippe Brucker
2023-05-18 13:59       ` Jason Gunthorpe
2023-05-18 16:49         ` Jean-Philippe Brucker
2023-05-18 18:17           ` Jason Gunthorpe
2023-05-10 15:37 ` Eric Auger
2023-05-10 16:20   ` Jean-Philippe Brucker

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=ZGT+44a6RYZ999kz@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=akihiko.odaki@daynix.com \
    --cc=eric.auger@redhat.com \
    --cc=iommu@lists.linux.dev \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=robin.murphy@arm.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=will@kernel.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).