[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120418184836.GB14635@redhat.com>
Date: Wed, 18 Apr 2012 21:48:38 +0300
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Paolo Bonzini <pbonzini@...hat.com>
Cc: linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org,
Amit Shah <amit.shah@...hat.com>,
Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [RFC PATCH] virtio_console: link vq to port with a private
pointer in struct virtqueue
On Wed, Apr 18, 2012 at 08:38:00PM +0200, Paolo Bonzini wrote:
> >>>> * @priv: a pointer for the virtqueue implementation to use.
> >>>> */
> >>>> struct virtqueue {
> >>>> @@ -21,6 +22,7 @@ struct virtqueue {
> >>>> void (*callback)(struct virtqueue *vq);
> >>>> const char *name;
> >>>> struct virtio_device *vdev;
> >>>> + void *vdev_priv;
> >>>> void *priv;
> >>>
> >>> The name is confusing: it seems to imply it's a device pointer.
> >>
> >> ... it's private to the driver that owns vdev, hence the name.
> >
> > I own a car but I'm not called Michael Car :)
> > driver_priv might be ok too. unfortunately virtio-pci
> > is also a driver so it can be misunderstood.
>
> Yes. Is fixing the comment and keeping the vdev_priv name ok with you?
This puts it lower on the scale of bad interfaces but
I think we still need a better name.
> > devices should dominate. ring is an implementation detail.
>
> Ring came first, ring gets the nice name. :)
>
> Paolo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists