[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH for-4.6 v2 7/8] python/xc: reinstate original implementation of next_bdf
On 27/07/2015 18:45, Wei Liu wrote: > I missed the fact that next_bdf is used to parsed user supplied > strings when reviewing. The user supplied string is a NULL-terminated > string separated by comma. User can supply several PCI devices in that > string. There is, however, no delimiter for different devices, hence > we can't change the syntax of that string. > > This patch reinstate the original implementation of next_bdf to > preserve the original syntax. The last argument for xc_assign_device > is always 0. > > Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> > --- > Cc: Tiejun Chen <tiejun.chen@xxxxxxxxx> > > Tiejun, are you actually using this python binding? I don't think we > have in tree user. > > If nobody is using it, I propose we remove this binding in next > release. > > I don't have live example of that string. My analysis is based on > reverse-engineering of original code. XenServer still uses a few methods from the lowlevel xc bindings, but this only extends to debug situations (our version of xen-bugtool) and I am not aware of us using this particular bit of the bindings. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |