From: Richard Henderson <rth@twiddle.net>
To: qemu-devel@nongnu.org
Subject: [Bug 1867072] Re: ARM: tag bits cleared in FAR_EL1
Date: Thu, 12 Mar 2020 16:04:56 -0000 [thread overview]
Message-ID: <158402909701.10809.1004399395866602664.malone@soybean.canonical.com> (raw)
In-Reply-To: 158397461074.11691.9165479040998830806.malonedeb@soybean.canonical.com
Ho hum, I must have been asleep last night.
Peter only merged 7 of 9 patches. The final 2 were re-posted:
https://patchew.org/QEMU/20200308012946.16303-1-richard.henderson@linaro.org/
which includes the critical change that affects FAR_ELx.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1867072
Title:
ARM: tag bits cleared in FAR_EL1
Status in QEMU:
In Progress
Bug description:
The ARM Architecture Reference Manual provides the following for
FAR_EL1:
"For a Data Abort or Watchpoint exception, if address tagging is
enabled for the address accessed by the data access that caused the
exception, then this field includes the tag."
However, I have found that the tag bits in FAR_EL1 are always clear,
even if the tag bits were set in the original access.
I can reproduce the problem on both 4.1.1 and master
(6e8a73e911f066527e775e04b98f31ebd19db600).
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1867072/+subscriptions
next prev parent reply other threads:[~2020-03-12 16:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 0:56 [Bug 1867072] [NEW] ARM: tag bits cleared in FAR_EL1 Peter Collingbourne
2020-03-12 4:59 ` [Bug 1867072] " Richard Henderson
2020-03-12 5:03 ` Richard Henderson
2020-03-12 16:04 ` Richard Henderson [this message]
2020-03-12 17:26 ` Peter Collingbourne
2020-03-15 23:21 ` Richard Henderson
2020-04-30 13:43 ` Laurent Vivier
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=158402909701.10809.1004399395866602664.malone@soybean.canonical.com \
--to=rth@twiddle.net \
--cc=1867072@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.