On 19 July 2016 at 10:22, Maxim Ostapenko wrote:
> On 18/07/16 18:51, Peter Maydell wrote:
>> Well, we do need to do some things:
>> * we're populating the PageDesc data structure which we later use
>> to cache generated code
>> * if we're marking the range as writeable and it wasn't previ
On 18/07/16 18:51, Peter Maydell wrote:
(CCing qemu-devel, which is more likely to get developer attention)
Peter, thank you for your answer.
On 18 July 2016 at 15:45, Maxim Ostapenko wrote:
1) AddressSanitizer mmaps quite large regions of memory for redzones and
shadow gap. In particular,
(CCing qemu-devel, which is more likely to get developer attention)
On 18 July 2016 at 15:45, Maxim Ostapenko wrote:
> 1) AddressSanitizer mmaps quite large regions of memory for redzones and
> shadow gap. In particular, for 39-bit AS it mmapes:
>
> || `[0x14, 0x1f]` || HighShadow
Hi!
When testing AddressSanitizer tool for AArch64 under qemu-aarch64 (user
mode), I found out that even trivial helloworld apps start extremely
slow (~2 seconds). I've investigated this a bit and noticed that QEMU
actually freezes in large mmaps and subsequent reads of /proc/self/maps.
Here
