From: Cornelia Huck <cohuck@redhat.com>
To: virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: [virtio] Re: [PATCH] iommu: offered -> negotiated
Date: Thu, 14 Apr 2022 11:11:06 +0200 [thread overview]
Message-ID: <87pmlk81xx.fsf@redhat.com> (raw)
In-Reply-To: <20220412083059.86367-1-cohuck@redhat.com>
On Tue, Apr 12 2022, Cornelia Huck <cohuck@redhat.com> wrote:
Hmm... it seems the original proposal had been too buried (or I actually
fat-fingered things in my patch).
What do we do now? Revert, and re-apply a new patch after perhaps some
further discussion? (Would likely be for 1.3, though. Maybe also vote,
as this does not seem to be as straightforward as I thought.)
> All those clauses actually apply whenever the feature is negotiated,
> not merely offered. Rename to clarify things.
>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
> virtio-iommu.tex | 10 +++++-----
> 1 file changed, 5 insertions(+), 5 deletions(-)
>
> diff --git a/virtio-iommu.tex b/virtio-iommu.tex
> index f8cbe8895f0d..efe1000ac2d2 100644
> --- a/virtio-iommu.tex
> +++ b/virtio-iommu.tex
> @@ -232,22 +232,22 @@ \subsection{Device operations}\label{sec:Device Types / IOMMU Device / Device op
> Creating mappings aligned on large page sizes can improve performance
> since they require fewer page table and TLB entries.
>
> -\item If the VIRTIO_IOMMU_F_DOMAIN_RANGE feature is offered,
> +\item If the VIRTIO_IOMMU_F_DOMAIN_RANGE feature is negotiated,
> \field{domain_range} describes the values supported in a \field{domain}
> - field. If the feature is not offered, any \field{domain} value is valid.
> + field. If the feature is not negotiated, any \field{domain} value is valid.
>
> -\item If the VIRTIO_IOMMU_F_INPUT_RANGE feature is offered,
> +\item If the VIRTIO_IOMMU_F_INPUT_RANGE feature is negotiated,
> \field{input_range} contains the virtual address range that the IOMMU is
> able to translate. Any mapping request to virtual addresses outside of
> this range fails.
>
> - If the feature is not offered, virtual mappings span over the whole
> + If the feature is not negotiated, virtual mappings span over the whole
> 64-bit address space (\texttt{start = 0, end = 0xffffffff ffffffff})
> \end{itemize}
>
> An endpoint is in bypass mode if:
> \begin{itemize}
> - \item the VIRTIO_IOMMU_F_BYPASS_CONFIG feature is offered and:
> + \item the VIRTIO_IOMMU_F_BYPASS_CONFIG feature is negotiated and:
> \begin{itemize}
> \item config field \field{bypass} is 1 and the endpoint is
> not attached to a domain. This applies even if the driver
> --
> 2.34.1
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
next prev parent reply other threads:[~2022-04-14 9:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 8:30 [PATCH] iommu: offered -> negotiated Cornelia Huck
2022-04-13 9:37 ` [virtio-comment] " Cornelia Huck
2022-04-13 12:51 ` [virtio] " Halil Pasic
2022-04-13 18:13 ` [virtio-comment] " Harald Mommer
2022-04-14 9:11 ` Cornelia Huck [this message]
2022-04-14 9:47 ` [virtio] " Halil Pasic
2022-04-19 9:52 ` Cornelia Huck
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=87pmlk81xx.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio@lists.oasis-open.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