On 03/08/2015 05:09, Fam Zheng wrote: > bdrv_probe_all is harder. If we modularize a format driver, its .bdrv_probe > code will be in the module. If we want to do the format detection, we need to > load all format drivers. This means if the command line has an unspecified > format, we'll still need to load all drivers at starting phase. (I wish all > formats are probed according to magic bytes at offset 0, so we can simplify > the > .bdrv_probe logic and do it with data matching in block.c like the protocol > case, but that's not true for VMDK :( )
I think it's okay to say that: - .bdrv_probe_device is not supported in modules (you have to use file.driver=foo manually) - not specifying a format results in all modules being loaded Paolo
