From: Christoffer Dall <cdall@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [PATCH] arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses
Date: Tue, 2 May 2017 09:30:26 +0200 [thread overview]
Message-ID: <20170502073026.GD16940@cbox> (raw)
In-Reply-To: <20170427180648.25159-1-marc.zyngier@arm.com>
On Thu, Apr 27, 2017 at 07:06:48PM +0100, Marc Zyngier wrote:
> Our 32bit CP14/15 handling inherited some of the ARMv7 code for handling
> the trapped system registers, completely missing the fact that the
> fields for Rt and Rt2 are now 5 bit wide, and not 4...
>
> Let's fix it, and provide an accessor for the most common Rt case.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Reviewed-by: Christoffer Dall <cdall@linaro.org>
Aplied to kvmarm/queue.
Thanks,
-Christoffer
prev parent reply other threads:[~2017-05-02 7:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-27 18:06 [PATCH] arm64: KVM: Fix decoding of Rt/Rt2 when trapping AArch32 CP accesses Marc Zyngier
2017-05-02 7:30 ` Christoffer Dall [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=20170502073026.GD16940@cbox \
--to=cdall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.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