Re: [Xen-devel] [PATCH 5/6] libxl: introduce libxl__alloc_vdev

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

Stefano Stabellini writes ("Re: [Xen-devel] [PATCH 5/6] libxl: introduce 
libxl__alloc_vdev"):
> I don't feel that strongly about this, but given that the naming scheme
> used in the guest is actually arbitrary at the moment (as in not document
> or well defined anywhere), I would start the dynamic space before the
> 26th device: I have the feeling that after "xvdz" the behavior is going
> to be even less "defined". I suggest "xvdm" as a starting point.

That's fine, if the starting point is configurable.

> > However, that does not mean that the guest should not document its
> > naming conventions.  Perhaps this needs to be clarified in the
> > document.
> 
> Right, but unless I am missing something there isn't such a thing at the
> moment, at least in Linux.
> 
> I'll try to come up with a linux devid to vdev function true to the
> original.

That would be good.  If you felt like documenting the Linux behaviour
properly that would be good.  The section "Notes on Linux as a guest"
in docs/misc/vbd-interface.text.

TBH I think Linux /should/ use the same numbering scheme as the name
supplied in the host config file, just for sanity's sake.

Ian.

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