From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:35460) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eieC3-0005r7-HX for qemu-devel@nongnu.org; Mon, 05 Feb 2018 05:40:17 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eieC0-0000mT-ET for qemu-devel@nongnu.org; Mon, 05 Feb 2018 05:40:11 -0500 Date: Mon, 5 Feb 2018 11:39:54 +0100 From: Igor Mammedov Message-ID: <20180205113954.4dc30b5f@redhat.com> In-Reply-To: References: <1512670493-18114-1-git-send-email-peter.maydell@linaro.org> <1512670493-18114-5-git-send-email-peter.maydell@linaro.org> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH 4/6] target/arm: Add "-cpu max" support List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Peter Maydell Cc: Philippe =?UTF-8?B?TWF0aGlldS1EYXVkw6k=?= , "patches@linaro.org" , qemu-arm , QEMU Developers , Eduardo Habkost , "Richard W . M . Jones" On Fri, 2 Feb 2018 17:54:43 +0000 Peter Maydell wrote: > On 26 January 2018 at 15:44, Philippe Mathieu-Daud=C3=A9 wrote: > > On 01/26/2018 11:33 AM, Peter Maydell wrote: =20 > >> On 26 January 2018 at 14:29, Philippe Mathieu-Daud=C3=A9 wrote: =20 > >>> Why not use arm_any_initfn() here? =20 > >> > >> That function (and the 'any' cpu) are deliberately only > >> included in the linux-user binaries, not the system-emulation binaries= . =20 > > > > why not use the V8 features? =20 >=20 > What v8 features? >=20 > >> (Also arm_any_initfn() only initializes userspace-visible stuff, it > >> doesn't provide ID register values etc for kernel-visible things.) =20 > > > > I'd still use an unique arm_max_initfn() such > > > > // initializes userspace-visible stuff > > #ifndef CONFIG_USER_ONLY > > // initializes kernel-visible things > > #endif =20 >=20 > >>> Actually what seems cleaner is to move "any" features here, and kill = the > >>> "any" cpu, using "max" for this purpose. =20 > >> > >> We can't kill 'any', that would break back-compatibility > >> of command lines. =20 > > > > and use an alias for 'any' -> 'max' or just I'd suggest to place easy any -> max compat hack into arm_cpu_class_by_name() > > > > { .name =3D "any", .initfn =3D arm_max_initfn }, /* backward compat *= / =20 >=20 > Yes, we could probably do something similar to this. >=20 > thanks > -- PMM >=20