Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: Cornelia Huck <cohuck@redhat.com>
To: Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: virtio-dev@lists.oasis-open.org, joro@8bytes.org,
	tnowicki@marvell.com, eric.auger@redhat.com,
	kevin.tian@intel.com, lorenzo.pieralisi@arm.com, mst@redhat.com,
	bauerman@linux.ibm.com
Subject: Re: [virtio-dev] [PATCH RESEND v4 1/1] Add virtio-iommu device specification
Date: Wed, 20 Nov 2019 18:27:34 +0100	[thread overview]
Message-ID: <20191120182734.7d6ec586.cohuck@redhat.com> (raw)
In-Reply-To: <20191120151903.175110-2-jean-philippe@linaro.org>

On Wed, 20 Nov 2019 16:19:03 +0100
Jean-Philippe Brucker <jean-philippe@linaro.org> wrote:

> The IOMMU device allows a guest to manage DMA mappings for physical,
> emulated and paravirtualized endpoints. Add device description for the
> virtio-iommu device and driver. Introduce PROBE, ATTACH, DETACH, MAP and
> UNMAP requests, as well as translation error reporting.
> 
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/37
> Signed-off-by: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>
> ---
>  conformance.tex  |  40 ++-
>  content.tex      |   1 +
>  virtio-iommu.tex | 816 +++++++++++++++++++++++++++++++++++++++++++++++
>  3 files changed, 855 insertions(+), 2 deletions(-)
>  create mode 100644 virtio-iommu.tex

Sorry about being late to the party, but I just started looking at this
when the voting went up :/

(...)

> diff --git a/virtio-iommu.tex b/virtio-iommu.tex
> new file mode 100644
> index 0000000..28c562b
> --- /dev/null
> +++ b/virtio-iommu.tex

(...)

> +\subsection{Device configuration layout}\label{sec:Device Types / IOMMU Device / Device configuration layout}
> +
> +The \field{page_size_mask} field is always present. Availability of the
> +others all depend on feature bits described in
> +\ref{sec:Device Types / IOMMU Device / Feature bits}.
> +
> +\begin{lstlisting}
> +struct virtio_iommu_config {
> +  le64 page_size_mask;
> +  struct virtio_iommu_range_64 {
> +    le64 start;
> +    le64 end;
> +  } input_range;
> +  struct virtio_iommu_range_32 {
> +    le32 start;
> +    le32 end;
> +  } domain_range;
> +  le32 probe_size;
> +};
> +\end{lstlisting}
> +
> +\drivernormative{\subsubsection}{Device configuration layout}{Device Types / IOMMU Device / Device configuration layout}
> +
> +The driver MUST NOT write to device configuration fields.
> +
> +\devicenormative{\subsubsection}{Device configuration layout}{Device Types / IOMMU Device / Device configuration layout}
> +
> +The device SHOULD set \field{padding} to zero.

I don't see any field named 'padding' -- is that a leftover from an
earlier version?

If it is, we can probably remove it as a trivial change on top after
this change went in.

> +
> +The device MUST set at least one bit in \field{page_size_mask}, describing
> +the page granularity. The device MAY set more than one bit in
> +\field{page_size_mask}.


---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2019-11-20 17:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 15:19 [virtio-dev] [PATCH RESEND v4 0/1] Add virtio-iommu specification Jean-Philippe Brucker
2019-11-20 15:19 ` [virtio-dev] [PATCH RESEND v4 1/1] Add virtio-iommu device specification Jean-Philippe Brucker
2019-11-20 17:27   ` Cornelia Huck [this message]
2019-11-20 17:44     ` Jean-Philippe Brucker
2019-11-20 21:56       ` Michael S. Tsirkin
2019-11-21  8:56       ` Cornelia Huck
2019-11-25  7:30   ` Jan Kiszka
2019-11-25 12:35     ` Jean-Philippe Brucker
2019-11-25 19:01       ` Jan Kiszka

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=20191120182734.7d6ec586.cohuck@redhat.com \
    --to=cohuck@redhat.com \
    --cc=bauerman@linux.ibm.com \
    --cc=eric.auger@redhat.com \
    --cc=jean-philippe@linaro.org \
    --cc=joro@8bytes.org \
    --cc=kevin.tian@intel.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mst@redhat.com \
    --cc=tnowicki@marvell.com \
    --cc=virtio-dev@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