Re: [PATCH] [PATCH] linux-user/aarch64: Reset target data on MADV_DONTNEED

2022-08-10 Thread Vitaly Buka
Sorry, I only noticed today that it's not submitted. Version is not critical for us, as we build from masters anyway. Richard, do you know a reason to consider this critical? On Wed, 10 Aug 2022 at 13:04, Peter Maydell wrote: > On Wed, 10 Aug 2022 at 21:00, Vitaly Buka wrote: > > &g

Re: [PATCH] [PATCH] linux-user/aarch64: Reset target data on MADV_DONTNEED

2022-08-10 Thread Vitaly Buka
How can we land this one?

[PATCH] [PATCH] linux-user/aarch64: Reset target data on MADV_DONTNEED

2022-07-11 Thread Vitaly Buka
aarch64 stores MTE tags in target_date, and they should be reset by MADV_DONTNEED. Signed-off-by: Vitaly Buka --- accel/tcg/translate-all.c | 24 include/exec/cpu-all.h| 1 + linux-user/mmap.c | 2 ++ 3 files changed, 27 insertions(+) diff --git a/accel

[Bug 1921948] Re: MTE tags not checked properly for unaligned accesses at EL1

2021-05-26 Thread Vitaly Buka
I see something similar in memset It SEGV on sturq0, [x4, #-16] for x4 set to 0xd55214fe008 and near tags are 0xd55214fdff0 and 0xd55214fe000 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU.

[Bug 1926521] Re: QEMU-user ignores MADV_DONTNEED

2021-05-15 Thread Vitaly Buka
New issue on GitLab https://gitlab.com/qemu-project/qemu/-/issues/326 ** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #326 https://gitlab.com/qemu-project/qemu/-/issues/326 -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to

[Bug 1926521] [NEW] QEMU-user ignores MADV_DONTNEED

2021-04-28 Thread Vitaly Buka
Public bug reported: There is comment int the code "This is a hint, so ignoring and returning success is ok" https://github.com/qemu/qemu/blob/b1cffefa1b163bce9aebc3416f562c1d3886eeaa/linux-user/syscall.c#L11941 But it seems incorrect with the current state of Linux "man madvise" or

Re: [Bug 1926044] Re: QEMU-user doesn't report HWCAP2_MTE

2021-04-27 Thread Vitaly Buka
Thanks for the quick fix! On Tue, Apr 27, 2021 at 2:55 PM Richard Henderson < 1926...@bugs.launchpad.net> wrote: > > https://patchew.org/QEMU/20210427214108.88503-1-richard.hender...@linaro.org/ > > This has missed 6.0, but should be acceptable to roll into 6.0.1. > > -- > You received this bug

[Bug 1926044] Re: QEMU-user doesn't report HWCAP2_MTE

2021-04-24 Thread Vitaly Buka
Sorry, 0 7 8 should be "HWCAP2_DCPODP HWCAP2_FLAGM2 HWCAP2_FRINT" -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1926044 Title: QEMU-user doesn't report HWCAP2_MTE Status in QEMU: New Bug

[Bug 1926044] Re: QEMU-user doesn't report HWCAP2_MTE

2021-04-24 Thread Vitaly Buka
Actually if we make it like this: #include #include int main(int ac, char **av) { for (int i = 0; i < 32; ++i) if ((int)(getauxval(AT_HWCAP2) & (1 << i))) printf("%d\n", i); } clang mytest.c -target aarch64-linux-gnu -fsanitize=memtag -march=armv8+memtag qemu-aarch64

[Bug 1926044] [NEW] QEMU-user doesn't report HWCAP2_MTE

2021-04-24 Thread Vitaly Buka
Public bug reported: Reproducible on ffa090bc56e73e287a63261e70ac02c0970be61a Host Debian 5.10.24 x86_64 GNU Configured with "configure --disable-system --enable-linux-user --static" This one works and prints "OK" as expected: clang tests/tcg/aarch64/mte-3.c -target aarch64-linux-gnu