From: Cornelia Huck <cohuck@redhat.com>
To: Halil Pasic <pasic@linux.ibm.com>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
virtio-comment@lists.oasis-open.org, stefanha@redhat.com
Subject: Re: [virtio-comment] [PATCH 1/3] shared memory: Define shared memory regions
Date: Tue, 15 Jan 2019 10:33:37 +0100 [thread overview]
Message-ID: <20190115103337.2f15e4e0.cohuck@redhat.com> (raw)
In-Reply-To: <20190111185717.2ebb286c@oc2783563651>
On Fri, 11 Jan 2019 18:57:17 +0100
Halil Pasic <pasic@linux.ibm.com> wrote:
> On Fri, 11 Jan 2019 16:07:23 +0000
> "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
>
> > > Do we want to change the device initialization (3.1) subsection? I'm not
> > > sure if this shared memory region discovery is something that's
> > > supposed to be a part of the initialization. At the moment, I would guess
> > > is the device not supposed to be able to provide new regions at any time
> > > (as I don't see how the device is supposed to tell the driver: hey
> > > please re-do discovery).
> >
> > Yes, it's part of initialisation; although since the enumeration is
> > specific to the transport and the use is specific to the device, I'm not
> > sure what goes in a common initialization section.
>
> I think it does go in a common initialization. Virtqueues are also
> discovered in a transport specific way, and same goes for reading/writing config.
>
> So I would add somethng to
> "7. Perform device-specific setup, including discovery of virtqueues for
> the device, optional per-bus setup, reading and possibly writing the
> device’s virtio configuration space, and population of virtqueues." in
> subsection 3.1.1.
Agreed, it probably makes sense to add shared memory region discovery
as an extra item to this list of things to be setup.
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-01-15 9:33 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 11:41 [virtio-comment] [PATCH 0/3] Large shared memory regions Dr. David Alan Gilbert (git)
2019-01-11 11:41 ` [virtio-comment] [PATCH 1/3] shared memory: Define " Dr. David Alan Gilbert (git)
2019-01-11 12:15 ` Cornelia Huck
2019-01-11 12:26 ` Dr. David Alan Gilbert
2019-01-15 10:10 ` Cornelia Huck
2019-01-15 11:23 ` Dr. David Alan Gilbert
2019-01-16 10:56 ` Cornelia Huck
2019-01-16 20:06 ` Dr. David Alan Gilbert
2019-02-11 21:52 ` Cornelia Huck
2019-02-13 18:37 ` Dr. David Alan Gilbert
2019-02-14 10:58 ` Cornelia Huck
2019-02-14 16:37 ` Dr. David Alan Gilbert
2019-02-14 17:43 ` Frank Yang
2019-02-15 11:07 ` Cornelia Huck
2019-02-15 11:19 ` Dr. David Alan Gilbert
2019-02-15 12:31 ` Cornelia Huck
2019-02-18 15:28 ` Halil Pasic
2019-02-15 11:26 ` David Hildenbrand
2019-02-15 12:28 ` Cornelia Huck
2019-02-15 12:33 ` David Hildenbrand
2019-02-15 12:37 ` Cornelia Huck
2019-02-15 12:59 ` David Hildenbrand
2019-02-15 13:50 ` Dr. David Alan Gilbert
2019-02-15 13:56 ` David Hildenbrand
2019-02-15 14:02 ` Dr. David Alan Gilbert
2019-02-15 14:13 ` David Hildenbrand
2019-02-15 15:14 ` Dr. David Alan Gilbert
2019-02-15 21:42 ` Halil Pasic
2019-02-15 22:08 ` David Hildenbrand
2019-02-15 12:51 ` Halil Pasic
2019-02-15 13:33 ` Cornelia Huck
2019-01-23 15:12 ` Michael S. Tsirkin
2019-01-11 15:29 ` Halil Pasic
2019-01-11 16:07 ` Dr. David Alan Gilbert
2019-01-11 17:57 ` Halil Pasic
2019-01-15 9:33 ` Cornelia Huck [this message]
2019-02-13 2:25 ` [virtio-comment] " Stefan Hajnoczi
2019-02-13 10:44 ` Dr. David Alan Gilbert
2019-02-14 3:43 ` Stefan Hajnoczi
2019-01-11 11:41 ` [virtio-comment] [PATCH 2/3] shared memory: Define PCI capability Dr. David Alan Gilbert (git)
2019-02-13 2:30 ` [virtio-comment] " Stefan Hajnoczi
2019-01-11 11:42 ` [virtio-comment] [PATCH 3/3] shared memory: Define mmio registers Dr. David Alan Gilbert (git)
2019-02-13 2:33 ` [virtio-comment] " Stefan Hajnoczi
2019-02-13 16:52 ` Dr. David Alan Gilbert
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=20190115103337.2f15e4e0.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@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