Re: [virtio-comment] [PATCH 1/3] shared memory: Define shared memory regions

[Cornelia Huck <cohuck@redhat.com>]

On Fri, 15 Feb 2019 13:51:34 +0100
Halil Pasic <pasic@linux.ibm.com> wrote:

> On Thu, 14 Feb 2019 11:58:07 +0100
> Cornelia Huck <cohuck@redhat.com> wrote:
> 
> > Tags: inv, virtio 
> > From: Cornelia Huck <cohuck@redhat.com>
> > To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> > Cc: virtio-comment@lists.oasis-open.org, stefanha@redhat.com, Halil Pasic <pasic@linux.ibm.com>
> > Subject: Re: [virtio-comment] [PATCH 1/3] shared memory: Define shared memory regions
> > Date: Thu, 14 Feb 2019 11:58:07 +0100
> > Sender: <virtio-comment@lists.oasis-open.org>
> > Organization: Red Hat GmbH
> > 
> > On Wed, 13 Feb 2019 18:37:56 +0000
> > "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> >   
> > > * Cornelia Huck (cohuck@redhat.com) wrote:    
> > > > On Wed, 16 Jan 2019 20:06:25 +0000
> > > > "Dr. David Alan Gilbert" <dgilbert@redhat.com> wrote:
> > > >       
> > > > > So these are all moving this 1/3 forward - has anyone got comments on
> > > > > the transport specific implementations?      
> > > > 
> > > > No comment on pci or mmio, but I've hacked something together for ccw.
> > > > Basically, one sense-type ccw for discovery and a control-type ccw for
> > > > activation of the regions (no idea if we really need the latter), both
> > > > available with ccw revision 3.
> > > > 
> > > > No idea whether this will work this way, though...      
> > > 
> > > That sounds (from a shm perspective) reasonable; can I ask why the
> > > 'activate' is needed?    
> > 
> > The activate interface is actually what I'm most unsure about; maybe
> > Halil can chime in.  
> 
> Sorry, I unfortunately kept deferring looking into this. Will have to do
> some more thinking. I promise to give you my feedback by Monday end of
> day if not sooner. Does that work with you?

Sure; please also take a look at DavidH's proposal.

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/