From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-arm] [PATCH 3/3] target/arm: Implement DBGVCR32_EL2 system register
Date: Thu, 12 Jan 2017 21:46:52 +0100 [thread overview]
Message-ID: <20170112204652.GA9606@toto> (raw)
In-Reply-To: <1484073849-32666-4-git-send-email-peter.maydell@linaro.org>
On Tue, Jan 10, 2017 at 06:44:09PM +0000, Peter Maydell wrote:
> The DBGVCR_EL2 system register is needed to run a 32-bit
> EL1 guest under a Linux EL2 64-bit hypervisor. Its only
> purpose is to provide AArch64 with access to the state of
> the DBGVCR AArch32 register. Since we only have a dummy
> DBGVCR, implement a corresponding dummy DBGVCR32_EL2.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> target/arm/helper.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index dc90986..bda562d 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -4066,6 +4066,13 @@ static const ARMCPRegInfo debug_cp_reginfo[] = {
> .cp = 14, .opc1 = 0, .crn = 0, .crm = 7, .opc2 = 0,
> .access = PL1_RW, .accessfn = access_tda,
> .type = ARM_CP_NOP },
> + /* Dummy DBGVCR32_EL2 (which is only for a 64-bit hypervisor
> + * to save and restore a 32-bit guest's DBGVCR)
> + */
> + { .name = "DBGVCR32_EL2", .state = ARM_CP_STATE_AA64,
> + .opc0 = 2, .opc1 = 4, .crn = 0, .crm = 7, .opc2 = 0,
> + .access = PL2_RW, .accessfn = access_tda,
> + .type = ARM_CP_NOP },
> /* Dummy MDCCINT_EL1, since we don't implement the Debug Communications
> * Channel but Linux may try to access this register. The 32-bit
> * alias is DBGDCCINT.
> --
> 2.7.4
>
WARNING: multiple messages have this Message-ID (diff)
From: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 3/3] target/arm: Implement DBGVCR32_EL2 system register
Date: Thu, 12 Jan 2017 21:46:52 +0100 [thread overview]
Message-ID: <20170112204652.GA9606@toto> (raw)
In-Reply-To: <1484073849-32666-4-git-send-email-peter.maydell@linaro.org>
On Tue, Jan 10, 2017 at 06:44:09PM +0000, Peter Maydell wrote:
> The DBGVCR_EL2 system register is needed to run a 32-bit
> EL1 guest under a Linux EL2 64-bit hypervisor. Its only
> purpose is to provide AArch64 with access to the state of
> the DBGVCR AArch32 register. Since we only have a dummy
> DBGVCR, implement a corresponding dummy DBGVCR32_EL2.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
Reviewed-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> target/arm/helper.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/target/arm/helper.c b/target/arm/helper.c
> index dc90986..bda562d 100644
> --- a/target/arm/helper.c
> +++ b/target/arm/helper.c
> @@ -4066,6 +4066,13 @@ static const ARMCPRegInfo debug_cp_reginfo[] = {
> .cp = 14, .opc1 = 0, .crn = 0, .crm = 7, .opc2 = 0,
> .access = PL1_RW, .accessfn = access_tda,
> .type = ARM_CP_NOP },
> + /* Dummy DBGVCR32_EL2 (which is only for a 64-bit hypervisor
> + * to save and restore a 32-bit guest's DBGVCR)
> + */
> + { .name = "DBGVCR32_EL2", .state = ARM_CP_STATE_AA64,
> + .opc0 = 2, .opc1 = 4, .crn = 0, .crm = 7, .opc2 = 0,
> + .access = PL2_RW, .accessfn = access_tda,
> + .type = ARM_CP_NOP },
> /* Dummy MDCCINT_EL1, since we don't implement the Debug Communications
> * Channel but Linux may try to access this register. The 32-bit
> * alias is DBGDCCINT.
> --
> 2.7.4
>
next prev parent reply other threads:[~2017-01-12 20:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 18:44 [Qemu-arm] [PATCH 0/3] target/arm: Support EL1 AArch32 guest under AArch64 EL2 Peter Maydell
2017-01-10 18:44 ` [Qemu-devel] " Peter Maydell
2017-01-10 18:44 ` [Qemu-arm] [PATCH 1/3] target/arm: A32, T32: Create Instruction Syndromes for Data Aborts Peter Maydell
2017-01-10 18:44 ` [Qemu-devel] " Peter Maydell
2017-01-12 20:41 ` [Qemu-arm] " Edgar E. Iglesias
2017-01-12 20:41 ` [Qemu-devel] " Edgar E. Iglesias
2017-01-12 21:50 ` [Qemu-arm] " Peter Maydell
2017-01-12 21:50 ` [Qemu-devel] " Peter Maydell
2017-01-10 18:44 ` [Qemu-arm] [PATCH 2/3] target/arm: Handle VIRQ and VFIQ in arm_cpu_do_interrupt_aarch32() Peter Maydell
2017-01-10 18:44 ` [Qemu-devel] " Peter Maydell
2017-01-12 21:41 ` [Qemu-arm] " Edgar E. Iglesias
2017-01-12 21:41 ` [Qemu-devel] " Edgar E. Iglesias
2017-01-10 18:44 ` [Qemu-arm] [PATCH 3/3] target/arm: Implement DBGVCR32_EL2 system register Peter Maydell
2017-01-10 18:44 ` [Qemu-devel] " Peter Maydell
2017-01-12 20:46 ` Edgar E. Iglesias [this message]
2017-01-12 20:46 ` Edgar E. Iglesias
2017-01-12 20:46 ` [Qemu-arm] [PATCH 0/3] target/arm: Support EL1 AArch32 guest under AArch64 EL2 Edgar E. Iglesias
2017-01-12 20:46 ` [Qemu-devel] " Edgar E. Iglesias
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=20170112204652.GA9606@toto \
--to=edgar.iglesias@gmail.com \
--cc=patches@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 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.