From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Stefan Hajnoczi <stefanha@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, cohuck@redhat.com,
sebastien.boeuf@intel.com
Subject: Re: [virtio-comment] [PATCH v3 1/3] shared memory: Define shared memory regions
Date: Thu, 7 Mar 2019 17:53:48 +0000 [thread overview]
Message-ID: <20190307175347.GL2811@work-vm> (raw)
In-Reply-To: <20190307162516.GH2843@stefanha-x1.localdomain>
* Stefan Hajnoczi (stefanha@redhat.com) wrote:
> On Mon, Mar 04, 2019 at 01:25:29PM +0000, Dr. David Alan Gilbert (git) wrote:
> > +\subsection{Addressing within regions}\label{sec:Basic Facilities of a Virtio Device / Shared Memory Regions / Addressing within regions }
> > +
> > +Commands sent over the virtqueues may refer to data within the
> > +shared memory regions, for example a command may be used by a
> > +driver to cause a device to add or remove a mapping within
> > +a region. When referring to data, the addresses will normally be
> > +offsets within a particular region rather than absolute host or
> > +guest addresses. The \field{shmid} may be explicit or may be
> > +inferred from the command type.
>
> This sounds like normative statements. They belong in a driver or
> device normative section.
I think we were trying in a previous version to make it one; but the
problem is it's not really a statement about something a device or
driver must do; it's a statement advising someone writing the spec
for a particular device to make sure it's specified like that.
> Otherwise:
>
> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Thanks.
Dave
--
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-03-07 17:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-04 13:25 [virtio-comment] [PATCH v3 0/3] Large shared memory regions Dr. David Alan Gilbert (git)
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 1/3] shared memory: Define " Dr. David Alan Gilbert (git)
2019-03-05 17:54 ` [virtio-comment] " Cornelia Huck
2019-03-07 16:25 ` [virtio-comment] " Stefan Hajnoczi
2019-03-07 17:53 ` Dr. David Alan Gilbert [this message]
2019-03-08 9:18 ` Stefan Hajnoczi
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-03-07 16:28 ` [virtio-comment] " Stefan Hajnoczi
2019-03-07 18:24 ` Dr. David Alan Gilbert
2019-03-08 9:19 ` Stefan Hajnoczi
2019-03-04 13:25 ` [virtio-comment] [PATCH v3 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-03-07 16:28 ` [virtio-comment] " Stefan Hajnoczi
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=20190307175347.GL2811@work-vm \
--to=dgilbert@redhat.com \
--cc=cohuck@redhat.com \
--cc=sebastien.boeuf@intel.com \
--cc=stefanha@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