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: Thu, 18 May 2023 10:59:12 -0300 [thread overview]
Message-ID: <ZGYvMDbkBN+2UgzG@nvidia.com> (raw)
In-Reply-To: <20230518135638.GB2587493@myrica>
On Thu, May 18, 2023 at 02:56:38PM +0100, Jean-Philippe Brucker wrote:
> > 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?
>
> Yes, I think the way the virtio-iommu driver should implement BLOCKED
> domains is initially clearing the global-bypass bit, and then issuing
> DETACH requests when the core asks to attach a BLOCKED domain. This has
> the same effect as issuing an ATTACH request with an empty domain, but
> requires fewer resources in the VMM.
Does that exclude identity though?
It seems like the protocol should not have an implicit operation like
this, the desired translation mode should always be made
explicit. Having a boot time default makes sense, but there is little
reason for an OS to go back to the boot time default...
Jason
next prev parent reply other threads:[~2023-05-18 13:59 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
2023-05-18 13:56 ` Jean-Philippe Brucker
2023-05-18 13:59 ` Jason Gunthorpe [this message]
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=ZGYvMDbkBN+2UgzG@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).