From: Peter Maydell <peter.maydell@linaro.org>
To: Mostafa Saleh <smostafa@google.com>
Cc: qemu-devel@nongnu.org, jean-philippe@linaro.org,
eric.auger@redhat.com, qemu-arm@nongnu.org,
richard.henderson@linaro.org
Subject: Re: [PATCH v5] hw/arm/smmuv3: Add GBPA register
Date: Tue, 14 Feb 2023 15:29:26 +0000 [thread overview]
Message-ID: <CAFEAcA98j4JhCytFsH_OPkxSkfhXRtX73cb9ieOmBOH6SFCR-g@mail.gmail.com> (raw)
In-Reply-To: <20230214094009.2445653-1-smostafa@google.com>
On Tue, 14 Feb 2023 at 09:40, Mostafa Saleh <smostafa@google.com> wrote:
>
> GBPA register can be used to globally abort all
> transactions.
>
> It is described in the SMMU manual in "6.3.14 SMMU_GBPA".
> ABORT reset value is IMPLEMENTATION DEFINED, it is chosen to
> be zero(Do not abort incoming transactions).
>
> Other fields have default values of Use Incoming.
>
> If UPDATE is not set, the write is ignored. This is the only permitted
> behavior in SMMUv3.2 and later.(6.3.14.1 Update procedure)
>
> As this patch adds a new state to the SMMU (GBPA), it is added
> in a new subsection for forward migration compatibility.
> GBPA is only migrated if its value is different from the reset value.
> It does this to be backward migration compatible if SW didn't write
> the register.
>
> Signed-off-by: Mostafa Saleh <smostafa@google.com>
> Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
> Reviewed-by: Eric Auger <eric.auger@redhat.com>
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2023-02-14 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 9:40 [PATCH v5] hw/arm/smmuv3: Add GBPA register Mostafa Saleh
2023-02-14 15:29 ` Peter Maydell [this message]
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=CAFEAcA98j4JhCytFsH_OPkxSkfhXRtX73cb9ieOmBOH6SFCR-g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=eric.auger@redhat.com \
--cc=jean-philippe@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=smostafa@google.com \
/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).