Re: [Xen-devel] [PATCH 04 of 16 RFC] blktap3: change libxl__blktap_devpath prototype to return an error code

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Mon, 2012-10-29 at 17:41 +0000, Thanos Makatos wrote:
> > -----Original Message-----
> > From: Ian Campbell
> > Sent: 26 October 2012 12:22
> > To: Thanos Makatos
> > Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] [PATCH 04 of 16 RFC] blktap3: change
> > libxl__blktap_devpath prototype to return an error code
> > 
> > On Wed, 2012-10-24 at 18:02 +0100, Thanos Makatos wrote:
> > > Make libxl__blktap_devpath return an error code instead of the
> > device,
> > > since there is no device in dom0 any more.
> > 
> > Does this function eventually go away then? Or will it eventually
> > return some sort of metadata which can be used to connect to the
> > created tap device?
> 
> As in blktap2, it creates the tapdisk process, but doesn't return any
> metadata, so it's still required. I guess changing the name of the
> function would clarify it.

Yes, I think that would be helpful.

Ian.


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel