Paolo Bonzini writes:
> On 10/11/2016 12:42, Alex Bennée wrote:
>>
>> Paolo Bonzini writes:
>>
>>> Computing TranslationBlock flags is pretty expensive on ARM, especially
>>> 32-bit. Because tbflags are computed on every tb lookup, it is not
>>> unlikely to see cpu_get_tb_cpu_state close to th
On 10/11/2016 12:42, Alex Bennée wrote:
>
> Paolo Bonzini writes:
>
>> Computing TranslationBlock flags is pretty expensive on ARM, especially
>> 32-bit. Because tbflags are computed on every tb lookup, it is not
>> unlikely to see cpu_get_tb_cpu_state close to the top of the profile
>> now t
Paolo Bonzini writes:
> Computing TranslationBlock flags is pretty expensive on ARM, especially
> 32-bit. Because tbflags are computed on every tb lookup, it is not
> unlikely to see cpu_get_tb_cpu_state close to the top of the profile
> now that QHT makes the hash table much more efficient.
>
On Mon, Sep 26, 2016 at 12:04 PM, Laurent Desnogues
wrote:
> Hello,
>
> On Wed, Sep 14, 2016 at 11:56 AM, Paolo Bonzini wrote:
>> Computing TranslationBlock flags is pretty expensive on ARM, especially
>> 32-bit. Because tbflags are computed on every tb lookup, it is not
>> unlikely to see cpu_g
Hello,
On Wed, Sep 14, 2016 at 11:56 AM, Paolo Bonzini wrote:
> Computing TranslationBlock flags is pretty expensive on ARM, especially
> 32-bit. Because tbflags are computed on every tb lookup, it is not
> unlikely to see cpu_get_tb_cpu_state close to the top of the profile
> now that QHT makes
Computing TranslationBlock flags is pretty expensive on ARM, especially
32-bit. Because tbflags are computed on every tb lookup, it is not
unlikely to see cpu_get_tb_cpu_state close to the top of the profile
now that QHT makes the hash table much more efficient.
However, most tbflags only change
