From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio-dev@lists.oasis-open.org,
virtio-comment@lists.oasis-open.org, stefanha@redhat.com,
vgoyal@redhat.com
Subject: [virtio-comment] Re: [PATCH v6 4/5] shared memory: Define PCI capability
Date: Fri, 12 Jul 2019 13:16:56 +0100 [thread overview]
Message-ID: <20190712121656.GI2730@work-vm> (raw)
In-Reply-To: <20190712110141.072c1365.cohuck@redhat.com>
* Cornelia Huck (cohuck@redhat.com) wrote:
> On Wed, 10 Jul 2019 19:32:11 +0100
> "Dr. David Alan Gilbert (git)" <dgilbert@redhat.com> wrote:
>
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > Define the PCI capability used for enumerating shared memory regions.
> >
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
> > ---
> > content.tex | 22 ++++++++++++++++++++++
> > 1 file changed, 22 insertions(+)
> >
>
> (...)
>
> > +\devicenormative{\paragraph}{Device-specific configuration}{Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / Shared memory capability}
>
> Sorry about not noticing that before, but doesn't that need to be
> referenced in the conformance section somewhere?
OK, new version coming up.
Dave
> > +
> > +The region defined by the combination of the \field {cap.offset},
> > +\field {cap.offset_hi}, and \field {cap.length}, \field
> > +{cap.length_hi} fields MUST be contained within the declared bar.
> > +
> > +The \field{cap.id} MUST be unique for any one device instance.
> > +
> > \subsubsection{PCI configuration access capability}\label{sec:Virtio Transport Options / Virtio Over PCI Bus / PCI Device Layout / PCI configuration access capability}
> >
> > The VIRTIO_PCI_CAP_PCI_CFG capability
>
> Otherwise, looks good.
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
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/
next prev parent reply other threads:[~2019-07-12 12:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 18:32 [virtio-comment] [PATCH v6 0/5] Large shared memory regions Dr. David Alan Gilbert (git)
2019-07-10 18:32 ` [virtio-comment] [PATCH v6 1/5] shared memory: Define " Dr. David Alan Gilbert (git)
2019-07-10 18:32 ` [virtio-comment] [PATCH v6 2/5] pci: Define id field Dr. David Alan Gilbert (git)
2019-07-12 8:58 ` [virtio-comment] " Cornelia Huck
2019-07-10 18:32 ` [virtio-comment] [PATCH v6 3/5] pci: Define virtio_pci_cap64 Dr. David Alan Gilbert (git)
2019-07-10 18:32 ` [virtio-comment] [PATCH v6 4/5] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-07-12 9:01 ` [virtio-comment] " Cornelia Huck
2019-07-12 12:16 ` Dr. David Alan Gilbert [this message]
2019-07-10 18:32 ` [virtio-comment] [PATCH v6 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=20190712121656.GI2730@work-vm \
--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