From: Julien Grall <julien@xen.org>
To: Ayan Kumar Halder <ayan.kumar.halder@amd.com>,
xen-devel@lists.xenproject.org
Cc: sstabellini@kernel.org, stefano.stabellini@amd.com,
Volodymyr_Babchuk@epam.com, bertrand.marquis@arm.com,
michal.orzel@amd.com
Subject: Re: [XEN v6 3/3] xen/arm: arm32: Add emulation of Debug Data Transfer Registers
Date: Tue, 12 Mar 2024 22:33:52 +0000 [thread overview]
Message-ID: <a60c8977-8a62-475f-a392-8f0c75bcd6c7@xen.org> (raw)
In-Reply-To: <20240307123943.1991755-4-ayan.kumar.halder@amd.com>
Hi Ayan,
On 07/03/2024 12:39, Ayan Kumar Halder wrote:
> When user enables HVC_DCC config option in Linux, it invokes access to debug
> transfer register (i.e. DBGDTRTXINT). As this register is not emulated, Xen
> injects an undefined exception to the guest and Linux crashes.
>
> To prevent this crash, introduce a partial emulation of DBGDTR[TR]XINT (these
> registers share the same encoding) as RAZ/WI and DBGDSCRINT as TXfull.
>
> Refer ARM DDI 0487J.a ID042523, G8.3.19, DBGDTRTXint:
> "If TXfull is set to 1, set DTRTX to UNKNOWN".
>
> As a pre-requisite, DBGOSLSR should be emulated in the same way as its AArch64
> variant (i.e. OSLSR_EL1). This is to ensure that DBGOSLSR.OSLK is 0, which
> allows us to skip the emulation of DBGDSCREXT (TXfull is treated as UNK/SBZP)
> and focus on DBGDSCRINT. DBGOSLSR.OSLM[1] is set to 1 to mantain consistency
> with Arm64.
>
> Take the opportunity to fix the minimum EL for DBGDSCRINT, which should be 0.
NIT: Strictly speaking Arm32 is using PL (Priviledge) rather than EL
(Exception Level) to describe each level :).
Anyway,
>
> Signed-off-by: Ayan Kumar Halder <ayan.kumar.halder@amd.com>
> Signed-off-by: Michal Orzel <michal.orzel@amd.com>
Acked-by: Julien Grall <jgrall@amazon.com>
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2024-03-12 22:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-07 12:39 [XEN v6 0/3] xen/arm: Add emulation of Debug Data Transfer Registers Ayan Kumar Halder
2024-03-07 12:39 ` [XEN v6 1/3] xen/arm: Introduce CONFIG_PARTIAL_EMULATION and "partial-emulation" cmd option Ayan Kumar Halder
2024-03-12 22:25 ` Julien Grall
2024-03-07 12:39 ` [XEN v6 2/3] xen/arm: arm64: Add emulation of Debug Data Transfer Registers Ayan Kumar Halder
2024-03-12 22:27 ` Julien Grall
2024-03-07 12:39 ` [XEN v6 3/3] xen/arm: arm32: " Ayan Kumar Halder
2024-03-12 22:33 ` Julien Grall [this message]
2024-03-14 13:05 ` [XEN v6 0/3] xen/arm: " Julien Grall
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=a60c8977-8a62-475f-a392-8f0c75bcd6c7@xen.org \
--to=julien@xen.org \
--cc=Volodymyr_Babchuk@epam.com \
--cc=ayan.kumar.halder@amd.com \
--cc=bertrand.marquis@arm.com \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=stefano.stabellini@amd.com \
--cc=xen-devel@lists.xenproject.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.