Jes Sorensen <jes.soren...@redhat.com> writes: > On 11/22/10 16:20, Anthony Liguori wrote: >> On 11/22/2010 09:10 AM, Jes Sorensen wrote: >>> On 11/22/10 16:08, Anthony Liguori wrote: >>>> On 11/22/2010 08:58 AM, Jes Sorensen wrote: >>>>> Right, the right solution is probably to create a block driver list >>>>> argument for configure, similar to what we have for the sound drivers. >>>>> >>>> --block-drv-whitelist= >>>> >>> Any idea what the difference is between 'whitelist' and 'list' in this >>> context? >> >> Everything is built, but only the formats that are in the whitelist are >> usable. > > Kinda defeats the purpose IMHO. It would be useful to be able to strip > out the formats one doesn't want to get a slimmed down binary.
There are two different purposes here: 1. You want to remove support for a format from QEMU and all the tools. That's what you have in mind, I think. 2. You want to distinguish between "good for production" and "not so good for production" formats. That's what the whitelist is for. Formats need to be whitelisted to be usable with QEMU proper. Tools normally ignore the whitelist. Lets you attempt offline format conversion for non-whitelisted formats, which is useful. Both are legitimate, in my opinion.