Re: [Qemu-devel] [PATCH v2 03/32] target/arm/cpu64: allow fp16 to be disabled

2018-02-21 Thread Richard Henderson
On 02/21/2018 08:35 AM, Alex Bennée wrote: >> Good news everybody -- this is an opportunity for a naming bikeshed >> discussion! ... >> * use the hwcaps names that Linux defines and prints in /proc/cpuinfo >>(in this case that would be a combination of "fphp" and "asimdhp", >>since hwcaps

Re: [Qemu-devel] [PATCH v2 03/32] target/arm/cpu64: allow fp16 to be disabled

2018-02-21 Thread Alex Bennée
Peter Maydell writes: > On 8 February 2018 at 17:31, Alex Bennée wrote: >> While for CONFIG_USER_ONLY it is policy for the "cpu" to be the most >> capable is can be this does cause problems. For example legacy RISU >> runs would fail as there

Re: [Qemu-devel] [PATCH v2 03/32] target/arm/cpu64: allow fp16 to be disabled

2018-02-13 Thread Peter Maydell
On 8 February 2018 at 17:31, Alex Bennée wrote: > While for CONFIG_USER_ONLY it is policy for the "cpu" to be the most > capable is can be this does cause problems. For example legacy RISU > runs would fail as there are a bunch of implemented instructions which > would

Re: [Qemu-devel] [PATCH v2 03/32] target/arm/cpu64: allow fp16 to be disabled

2018-02-08 Thread Richard Henderson
On 02/08/2018 09:31 AM, Alex Bennée wrote: > While for CONFIG_USER_ONLY it is policy for the "cpu" to be the most > capable is can be this does cause problems. For example legacy RISU > runs would fail as there are a bunch of implemented instructions which > would have caused failures that now