On Tue, May 26, 2015 at 06:51:18PM +0200, Paolo Bonzini wrote: > > > On 26/05/2015 18:40, Eduardo Habkost wrote: > > > What is the usecase? Was /etc/qemu/target-*.conf actually meant to be > > > user-customizable when it hosted the CPU models? > > > > I don't know what's the use case, that's why I think we should really > > remove it. I only want to warn users before removing it, because I don't > > know if people are using it for anything else. > > There are definitely usecases for qemu.conf (iqn/username/password > tuples for libiscsi, globally disabling KSM or memory dumps, globally > enabling timestamps). Not that anyone's using it, but I would leave it > alone. > > However, I don't think target-x86_64.conf would be missed, and it's > traditionally been something that is "owned by the package" (because the > CPU models were there) so we should be able to treat it as private.
You convinced me. We can apply this patch and if we change our minds before 2.4.0 we can easily revert just the one-line arch_init.c. So there's no need to split this patch in two, anymore. -- Eduardo
