From: Peter Maydell <peter.maydell@linaro.org>
To: "Edgar E. Iglesias" <edgar.iglesias@gmail.com>
Cc: Edgar Iglesias <edgar.iglesias@xilinx.com>,
qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH v1 1/1] target-arm: Mark CNTHP_TVAL_EL2 as ARM_CP_NO_RAW
Date: Fri, 26 Feb 2016 13:36:40 +0000 [thread overview]
Message-ID: <CAFEAcA--qxpgFcCnW5WdmTXwL4tjZGFBELSNUUTc0X-NhB-68w@mail.gmail.com> (raw)
In-Reply-To: <1456490739-19343-1-git-send-email-edgar.iglesias@gmail.com>
On 26 February 2016 at 12:45, Edgar E. Iglesias
<edgar.iglesias@gmail.com> wrote:
> From: "Edgar E. Iglesias" <edgar.iglesias@xilinx.com>
>
> Mark CNTHP_TVAL_EL2 as ARM_CP_NO_RAW due to the register not
> having any underlying state. This fixes an issue with booting
> KVM enabled kernels when EL2 is on.
>
> Signed-off-by: Edgar E. Iglesias <edgar.iglesias@xilinx.com>
> ---
> target-arm/helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/target-arm/helper.c b/target-arm/helper.c
> index 85a6685..601e3c1 100644
> --- a/target-arm/helper.c
> +++ b/target-arm/helper.c
> @@ -3631,7 +3631,7 @@ static const ARMCPRegInfo el2_cp_reginfo[] = {
> .writefn = gt_hyp_cval_write, .raw_writefn = raw_write },
> { .name = "CNTHP_TVAL_EL2", .state = ARM_CP_STATE_BOTH,
> .opc0 = 3, .opc1 = 4, .crn = 14, .crm = 2, .opc2 = 0,
> - .type = ARM_CP_IO, .access = PL2_RW,
> + .type = ARM_CP_NO_RAW | ARM_CP_IO, .access = PL2_RW,
> .resetfn = gt_hyp_timer_reset,
> .readfn = gt_hyp_tval_read, .writefn = gt_hyp_tval_write },
> { .name = "CNTHP_CTL_EL2", .state = ARM_CP_STATE_BOTH,
> --
Applied to target-arm.next, thanks.
-- PMM
prev parent reply other threads:[~2016-02-26 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 12:45 [Qemu-devel] [PATCH v1 1/1] target-arm: Mark CNTHP_TVAL_EL2 as ARM_CP_NO_RAW Edgar E. Iglesias
2016-02-26 13:36 ` 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=CAFEAcA--qxpgFcCnW5WdmTXwL4tjZGFBELSNUUTc0X-NhB-68w@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=edgar.iglesias@gmail.com \
--cc=edgar.iglesias@xilinx.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).