From: Vitaly Buka <1926044@bugs.launchpad.net>
To: qemu-devel@nongnu.org
Subject: Re: [Bug 1926044] Re: QEMU-user doesn't report HWCAP2_MTE
Date: Tue, 27 Apr 2021 23:58:46 -0000 [thread overview]
Message-ID: <CAMr+8yQy-QZrqOhEpaFB1sQ0iuT2gncL5r4eNzTSWON_noZMzg@mail.gmail.com> (raw)
In-Reply-To: 161956001517.10625.2379653538605536900.malone@soybean.canonical.com
Thanks for the quick fix!
On Tue, Apr 27, 2021 at 2:55 PM Richard Henderson <
1926044@bugs.launchpad.net> wrote:
>
> https://patchew.org/QEMU/20210427214108.88503-1-richard.henderson@linaro.org/
>
> This has missed 6.0, but should be acceptable to roll into 6.0.1.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1926044
>
> Title:
> QEMU-user doesn't report HWCAP2_MTE
>
> Status in QEMU:
> In Progress
>
> Bug description:
> 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
> -fsanitize=memtag -march=armv8+memtag
> qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out && echo OK
>
>
> This one fails and print "0":
> cat mytest.c
> #include <stdio.h>
> #include <sys/auxv.h>
>
> #ifndef HWCAP2_MTE
> #define HWCAP2_MTE (1 << 18)
> #endif
>
> int main(int ac, char **av)
> {
> printf("%d\n", (int)(getauxval(AT_HWCAP2) & HWCAP2_MTE));
> }
>
>
> clang mytest.c -target aarch64-linux-gnu -fsanitize=memtag
> -march=armv8+memtag
> qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/qemu/+bug/1926044/+subscriptions
>
--
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:
In Progress
Bug description:
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 -fsanitize=memtag -march=armv8+memtag
qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out && echo OK
This one fails and print "0":
cat mytest.c
#include <stdio.h>
#include <sys/auxv.h>
#ifndef HWCAP2_MTE
#define HWCAP2_MTE (1 << 18)
#endif
int main(int ac, char **av)
{
printf("%d\n", (int)(getauxval(AT_HWCAP2) & HWCAP2_MTE));
}
clang mytest.c -target aarch64-linux-gnu -fsanitize=memtag -march=armv8+memtag
qemu-aarch64 --cpu max -L /usr/aarch64-linux-gnu ./a.out
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1926044/+subscriptions
next prev parent reply other threads:[~2021-04-28 0:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-25 2:32 [Bug 1926044] [NEW] QEMU-user doesn't report HWCAP2_MTE Vitaly Buka
2021-04-25 2:45 ` [Bug 1926044] " Vitaly Buka
2021-04-25 2:47 ` Vitaly Buka
2021-04-25 18:39 ` Peter Maydell
2021-04-25 19:20 ` Richard Henderson
2021-04-27 21:46 ` Richard Henderson
2021-04-27 23:58 ` Vitaly Buka [this message]
2021-04-29 10:54 ` Thomas Huth
2021-05-26 15:42 ` Thomas Huth
2021-08-25 7:10 ` Thomas Huth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAMr+8yQy-QZrqOhEpaFB1sQ0iuT2gncL5r4eNzTSWON_noZMzg@mail.gmail.com \
--to=1926044@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).