[Qemu-devel] Re: [PATCH v5 4/5] Inter-VM shared memory PCI device

[Avi Kivity]

On 05/10/2010 06:22 PM, Cam Macdonell wrote:
> > > +
> > > +    /* if the position is -1, then it's shared memory region fd */
> > > +    if (incoming_posn == -1) {
> > > +
> > > +        s->num_eventfds = 0;
> > > +
> > > +        if (check_shm_size(s, incoming_fd) == -1) {
> > > +            exit(-1);
> > > +        }
> > > +
> > > +        /* creating a BAR in qemu_chr callback may be crazy */
> > > +        create_shared_memory_BAR(s, incoming_fd);
> > >
> > >        
> > It probably is... why can't you create it during initialization?
> >      
> This is for the shared memory server implementation, so the fd for the
> shared memory has to be received (over the qemu char device) from the
> server before the BAR can be created via qemu_ram_mmap() which adds
> the necessary memory
>
>    


We could do the handshake during initialization.  I'm worried that the 
device will appear without the BAR, and strange things will happen.  But 
the chardev API is probably not geared for passing data during init.

Anthony, any ideas?

> Otherwise, if the BAR is allocated during initialization, I would have
> to use MAP_FIXED to mmap the memory.  This is what I did before the
> qemu_ram_mmap() function was added.
>    

What would happen to any data written to the BAR before the the 
handshake completed?  I think it would disappear.

So it's a good idea to make the initialization process atomic.

--
error compiling committee.c: too many arguments to function