qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] target/arm: Declare support for FEAT_RASv1p1
Date: Tue, 31 May 2022 07:36:00 -0700	[thread overview]
Message-ID: <ed287f11-a910-89a6-18e0-5ee3ba6c39d5@linaro.org> (raw)
In-Reply-To: <20220531114258.855804-1-peter.maydell@linaro.org>

On 5/31/22 04:42, Peter Maydell wrote:
> The architectural feature RASv1p1 introduces the following new
> features:
>   * new registers ERXPFGCDN_EL1, ERXPFGCTL_EL1 and ERXPFGF_EL1
>   * new bits in the fine-grained trap registers that control traps
>     for these new registers
>   * new trap bits HCR_EL2.FIEN and SCR_EL3.FIEN that control traps
>     for ERXPFGCDN_EL1, ERXPFGCTL_EL1, ERXPFGP_EL1
>   * a larger number of the ERXMISC<n>_EL1 registers
>   * the format of ERR<n>STATUS registers changes
> 
> The architecture permits that if ERRIDR_EL1.NUM is 0 (as it is for
> QEMU) then all these new registers may UNDEF, and the HCR_EL2.FIEN
> and SCR_EL3.FIEN bits may be RES0.  We don't have any ERR<n>STATUS
> registers (again, because ERRIDR_EL1.NUM is 0).  QEMU does not yet
> implement the fine-grained-trap extension.  So there is nothing we
> need to implement to be compliant with the feature spec.  Make the
> 'max' CPU report the feature in its ID registers, and document it.
> 
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>

Reviewed-by: Richard Henderson <richard.henderson@linaro.org>


r~


      reply	other threads:[~2022-05-31 14:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 11:42 [PATCH] target/arm: Declare support for FEAT_RASv1p1 Peter Maydell
2022-05-31 14:36 ` Richard Henderson [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=ed287f11-a910-89a6-18e0-5ee3ba6c39d5@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=peter.maydell@linaro.org \
    --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).