From: Joe Komlodi <joe.komlodi@xilinx.com>
To: <qemu-devel@nongnu.org>
Cc: eric.auger@redhat.com, qemu-arm@nongnu.org
Subject: [PATCH 0/1] hw/arm/smmu: Add access flag handling
Date: Fri, 30 Jul 2021 16:17:01 -0700 [thread overview]
Message-ID: <1627687022-366528-1-git-send-email-joe.komlodi@xilinx.com> (raw)
Hi all,
This adds a check in SMMU PTW to see if the access flag bit is set in a PTE, and
if we should fault accordingly or not.
Since we do not support HTTU, the check itself is pretty simple:
If AFFD == 0 in the context descriptor and AF == 0 in the PTE, we fault.
Otherwise, we do not have an access fault.
Thanks!
Joe
Joe Komlodi (1):
hw/arm/smmu: Add access flag handling
hw/arm/smmu-common.c | 7 +++++++
hw/arm/smmu-internal.h | 8 ++++++++
hw/arm/smmuv3-internal.h | 1 +
hw/arm/smmuv3.c | 1 +
include/hw/arm/smmu-common.h | 1 +
5 files changed, 18 insertions(+)
--
2.7.4
next reply other threads:[~2021-07-30 23:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 23:17 Joe Komlodi [this message]
2021-07-30 23:17 ` [PATCH 1/1] hw/arm/smmu: Add access flag handling Joe Komlodi
2021-08-04 16:45 ` Eric Auger
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=1627687022-366528-1-git-send-email-joe.komlodi@xilinx.com \
--to=joe.komlodi@xilinx.com \
--cc=eric.auger@redhat.com \
--cc=qemu-arm@nongnu.org \
--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).