Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com>
To: virtio-dev@lists.oasis-open.org,
	virtio-comment@lists.oasis-open.org, stefanha@redhat.com,
	cohuck@redhat.com
Cc: vgoyal@redhat.com
Subject: [virtio-comment] [PATCH v7 3/5] pci: Define virtio_pci_cap64
Date: Fri, 12 Jul 2019 13:20:00 +0100	[thread overview]
Message-ID: <20190712122002.10793-4-dgilbert@redhat.com> (raw)
In-Reply-To: <20190712122002.10793-1-dgilbert@redhat.com>

From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>

Define 'virtio_pci_cap64' to allow capabilities to describe
memory regions larger than, or with an offset larger than 4GiB.

This will be used by the shared memory region capability.

Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
---
 content.tex | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/content.tex b/content.tex
index fafa532..d481359 100644
--- a/content.tex
+++ b/content.tex
@@ -746,6 +746,23 @@ \subsection{Virtio Structure PCI Capabilities}\label{sec:Virtio Transport Option
         \end{note}
 \end{description}
 
+A variant of this type, struct virtio_pci_cap64, is defined for
+those capaibilites that require offsets or lengths larger than
+4GiB:
+
+\begin{lstlisting}
+struct virtio_pci_cap64 {
+        struct virtio_pci_cap cap;
+        u32 offset_hi;
+        u32 length_hi;
+};
+\end{lstlisting}
+
+Given that the \field{cap.length} and \field{cap.offset} fields
+are only 32 bit, the additional \field{offset_hi} and \field {length_hi}
+fields provide the most significant 32 bits of a total 64 bit offset and
+length within the bar specified by \field{cap.bar}.
+
 \drivernormative{\subsubsection}{Virtio Structure PCI Capabilities}{Virtio Transport Options / Virtio Over PCI Bus / Virtio Structure PCI Capabilities}
 
 The driver MUST ignore any vendor-specific capability structure which has
-- 
2.21.0


This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  parent reply	other threads:[~2019-07-12 12:20 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-12 12:19 [virtio-comment] [PATCH v7 0/5] Large shared memory regions Dr. David Alan Gilbert (git)
2019-07-12 12:19 ` [virtio-comment] [PATCH v7 1/5] shared memory: Define " Dr. David Alan Gilbert (git)
2019-07-12 12:19 ` [virtio-comment] [PATCH v7 2/5] pci: Define id field Dr. David Alan Gilbert (git)
2019-07-12 12:20 ` Dr. David Alan Gilbert (git) [this message]
2019-07-29 15:40   ` [virtio-dev] [PATCH v7 3/5] pci: Define virtio_pci_cap64 Nikos Dragazis
2019-07-29 15:48     ` [virtio-comment] " Dr. David Alan Gilbert
2019-07-31 12:12       ` [virtio-dev] [PATCH] content: fix typo Nikos Dragazis
2019-07-31 12:18         ` Cornelia Huck
2019-07-12 12:20 ` [virtio-comment] [PATCH v7 4/5] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-07-12 12:48   ` [virtio-comment] " Cornelia Huck
2019-07-12 13:41     ` Dr. David Alan Gilbert
2019-07-12 12:20 ` [virtio-comment] [PATCH v7 5/5] shared memory: Define mmio registers Dr. David Alan Gilbert (git)

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=20190712122002.10793-4-dgilbert@redhat.com \
    --to=dgilbert@redhat.com \
    --cc=cohuck@redhat.com \
    --cc=stefanha@redhat.com \
    --cc=vgoyal@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --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