From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45091) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxI4d-0007ku-8C for qemu-devel@nongnu.org; Tue, 26 May 2015 12:51:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YxI4Z-000354-8i for qemu-devel@nongnu.org; Tue, 26 May 2015 12:51:27 -0400 Received: from mx1.redhat.com ([209.132.183.28]:49808) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YxI4Z-000350-3n for qemu-devel@nongnu.org; Tue, 26 May 2015 12:51:23 -0400 Message-ID: <5564A486.9030601@redhat.com> Date: Tue, 26 May 2015 18:51:18 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <55645794.3020202@redhat.com> <1432644847-7566-1-git-send-email-michael.i.doherty@intel.com> <55647C8D.2090006@redhat.com> <20150526162512.GS17796@thinpad.lan.raisama.net> <55649F65.60807@redhat.com> <20150526164026.GL28075@thinpad.lan.raisama.net> In-Reply-To: <20150526164026.GL28075@thinpad.lan.raisama.net> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH v3 1/2] arch_init: Drop target-x86_64.conf List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost Cc: Ikey Doherty , qemu-devel@nongnu.org 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. Paolo