From: christoffer.dall@arm.com (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 4/4] KVM: arm: vgic-v3: Add support for ICC_SGI0R and ICC_ASGI1R accesses
Date: Thu, 9 Aug 2018 09:41:53 +0200 [thread overview]
Message-ID: <20180809074153.GF20606@e113682-lin.lund.arm.com> (raw)
In-Reply-To: <20180808131501.584-5-marc.zyngier@arm.com>
On Wed, Aug 08, 2018 at 02:15:01PM +0100, Marc Zyngier wrote:
> In order to generate Group0 SGIs, let's add some decoding logic to
> access_gic_sgi(), and pass the generating group accordingly.
>
> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
> ---
> arch/arm/kvm/coproc.c | 25 ++++++++++++++++++++++++-
> 1 file changed, 24 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/kvm/coproc.c b/arch/arm/kvm/coproc.c
> index ec517992c12d..0dc0ca061d78 100644
> --- a/arch/arm/kvm/coproc.c
> +++ b/arch/arm/kvm/coproc.c
> @@ -246,6 +246,7 @@ static bool access_gic_sgi(struct kvm_vcpu *vcpu,
> const struct coproc_reg *r)
> {
> u64 reg;
> + int group;
>
> if (!p->is_write)
> return read_from_write_only(vcpu, p);
> @@ -253,7 +254,25 @@ static bool access_gic_sgi(struct kvm_vcpu *vcpu,
> reg = (u64)*vcpu_reg(vcpu, p->Rt2) << 32;
> reg |= *vcpu_reg(vcpu, p->Rt1) ;
>
> - vgic_v3_dispatch_sgi(vcpu, reg, 1);
> + /*
> + * In a system where GICD_CTLR.DS=1, a ICC_SGI0R access generates
> + * Group0 SGIs only, while ICC_SGI1R can generate either group,
> + * depending on the SGI configuration. ICC_ASGI1R is effectively
> + * equivalent to ICC_SGI0R, as there is no "alternative" secure
> + * group.
> + */
> + switch (p->Op1) {
> + default: /* Keep GCC quiet */
> + case 0: /* ICC_SGI1R */
> + group = 1;
> + break;
> + case 1: /* ICC_ASGI1R */
> + case 2: /* ICC_SGI0R */
> + group = 0;
> + break;
> + }
> +
> + vgic_v3_dispatch_sgi(vcpu, reg, group);
>
> return true;
> }
> @@ -459,6 +478,10 @@ static const struct coproc_reg cp15_regs[] = {
>
> /* ICC_SGI1R */
> { CRm64(12), Op1( 0), is64, access_gic_sgi},
> + /* ICC_ASGI1R */
> + { CRm64(12), Op1( 1), is64, access_gic_sgi},
> + /* ICC_SGI0R */
> + { CRm64(12), Op1( 2), is64, access_gic_sgi},
>
> /* VBAR: swapped by interrupt.S. */
> { CRn(12), CRm( 0), Op1( 0), Op2( 0), is32,
> --
> 2.18.0
>
Reviewed-by: Christoffer Dall <christoffer.dall@arm.com>
next prev parent reply other threads:[~2018-08-09 7:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-08 13:14 [PATCH 0/4] KVM: arm/arm64: vgic-v3: Group0 SGI support Marc Zyngier
2018-08-08 13:14 ` [PATCH 1/4] KVM: arm64: Remove non-existent AArch32 ICC_SGI1R encoding Marc Zyngier
2018-08-09 7:41 ` Christoffer Dall
2018-08-08 13:14 ` [PATCH 2/4] KVM: arm/arm64: vgic-v3: Add core support for Group0 SGIs Marc Zyngier
2018-08-09 7:40 ` Christoffer Dall
2018-08-09 11:59 ` Marc Zyngier
2018-08-08 13:15 ` [PATCH 3/4] KVM: arm64: vgic-v3: Add support for ICC_SGI0R_EL1 and ICC_ASGI1R_EL1 accesses Marc Zyngier
2018-08-09 7:41 ` Christoffer Dall
2018-08-08 13:15 ` [PATCH 4/4] KVM: arm: vgic-v3: Add support for ICC_SGI0R and ICC_ASGI1R accesses Marc Zyngier
2018-08-09 7:41 ` Christoffer Dall [this message]
2018-08-09 11:51 ` [PATCH 0/4] KVM: arm/arm64: vgic-v3: Group0 SGI support Auger Eric
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=20180809074153.GF20606@e113682-lin.lund.arm.com \
--to=christoffer.dall@arm.com \
--cc=linux-arm-kernel@lists.infradead.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).