24/01/2018 10:28, Yuanhan Liu: > On Wed, Jan 24, 2018 at 09:19:10AM +0100, Thomas Monjalon wrote: > > 24/01/2018 07:43, Yuanhan Liu: > > > On Tue, Jan 23, 2018 at 03:29:34PM +0100, Thomas Monjalon wrote: > > > > 23/01/2018 13:46, Yuanhan Liu: > > > > > If port not found, then the whole string will be used for dev > > > > > attachment. > > > > > It means we are attaching a port with PCI BDF == 04.00.0 AND > > > > > port == 0 (the 2nd port will not be attached). > > > > > > > > > > > > > > > And here is how the devargs would look like if "matching;settings" is > > > > > being used: > > > > > > > > > > > > > > > bus=pci,id=04:00.0/class=eth,port=0;bus=pci,id=04:00.0/class=eth,port=0/driver=mlx4,mlx4_arg_A=val,... > > > > > > > > > > The part before ";" will be used for lookup and the later part will be > > > > > used for attachment. It should work. It just looks redundant. > > > > > > > > It does not have to be redundant. > > > > It can be: > > > > > > > > bus=pci,id=04:00.0/class=eth,port=0;driver=mlx4,mlx4_arg1=settings1,... > > > > > > I knew you would make such reply :) > > > Then there is a contradiction. According your suggestion, the "port=0" > > > belongs > > > to the matching section, but it also has to be used in the settings > > > section. > > > > If port=0 is matched, it is already set, right? > > Yes. > > > Why it needs to be in settings? > > But I was talking the case it's not matched, say it's not probed and here > we do hotplug.
I don't understand. Anyway, the port property should be read-only. Are we talking about the dev_port from the Linux kernel?
