On 26/05/2015 18:25, Eduardo Habkost wrote:
> Can you separate this into two patches? First deleting the empty
> target-x86_64.conf file from the tree & Makefile, then another patch
> deleting the
> { CONFIG_QEMU_CONFDIR "/target-" TARGET_NAME ".conf", true }
> line in arch_init.c?
>
> We can delete sysconfigs/target/target-x86_64.conf from our source tree
> immediately, but I am not sure we should disable loading of
> /etc/qemu/target-*.conf with no warning (users may have their own
> target-*.conf files in their systems).
What is the usecase? Was /etc/qemu/target-*.conf actually meant to be
user-customizable when it hosted the CPU models?
Paolo
> We should probably warn about it in the 2.4 release announcement, and
> remove the arch_init.c line in 2.5.
>
> I would even go further and argue for removing /etc/qemu config file
> auto-loading entirely in QEMU 2.5 (including qemu.conf and
> target-*.conf).
