From: Mario Smarduch <m.smarduch@samsung.com>
To: Mario Smarduch <m.smarduch@samsung.com>
Cc: marc.zyngier@arm.com, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [RESEND PATCH v2 2/2] arm: KVM: keep arm vfp/simd exit handling consistent with arm64
Date: Sun, 21 Jun 2015 20:17:22 -0700 [thread overview]
Message-ID: <55877E42.5070205@samsung.com> (raw)
In-Reply-To: <1434739306-23417-1-git-send-email-m.smarduch@samsung.com>
On 06/19/2015 11:41 AM, Mario Smarduch wrote:
[...]
>
>
> -host_switch_to_hyp:
> + /* Guest is calling a hyp function, save minimum context branch to it */
Hi Marc,
please correct Guest to Host (or word this to your preference).
Somehow wondered off on Friday :)
Thanks,
- Mario
> pop {r0, r1, r2}
>
> /* Check for __hyp_get_vectors */
> @@ -411,6 +407,10 @@ guest_trap:
>
> @ Check if we need the fault information
> lsr r1, r1, #HSR_EC_SHIFT
> +#ifdef CONFIG_VFPv3
> + cmp r1, #HSR_EC_CP_0_13
> + beq switch_to_guest_vfp
> +#endif
> cmp r1, #HSR_EC_IABT
> mrceq p15, 4, r2, c6, c0, 2 @ HIFAR
> beq 2f
>
WARNING: multiple messages have this Message-ID (diff)
From: m.smarduch@samsung.com (Mario Smarduch)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH v2 2/2] arm: KVM: keep arm vfp/simd exit handling consistent with arm64
Date: Sun, 21 Jun 2015 20:17:22 -0700 [thread overview]
Message-ID: <55877E42.5070205@samsung.com> (raw)
In-Reply-To: <1434739306-23417-1-git-send-email-m.smarduch@samsung.com>
On 06/19/2015 11:41 AM, Mario Smarduch wrote:
[...]
>
>
> -host_switch_to_hyp:
> + /* Guest is calling a hyp function, save minimum context branch to it */
Hi Marc,
please correct Guest to Host (or word this to your preference).
Somehow wondered off on Friday :)
Thanks,
- Mario
> pop {r0, r1, r2}
>
> /* Check for __hyp_get_vectors */
> @@ -411,6 +407,10 @@ guest_trap:
>
> @ Check if we need the fault information
> lsr r1, r1, #HSR_EC_SHIFT
> +#ifdef CONFIG_VFPv3
> + cmp r1, #HSR_EC_CP_0_13
> + beq switch_to_guest_vfp
> +#endif
> cmp r1, #HSR_EC_IABT
> mrceq p15, 4, r2, c6, c0, 2 @ HIFAR
> beq 2f
>
next prev parent reply other threads:[~2015-06-22 3:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 18:41 [RESEND PATCH v2 2/2] arm: KVM: keep arm vfp/simd exit handling consistent with arm64 Mario Smarduch
2015-06-19 18:41 ` Mario Smarduch
2015-06-22 3:17 ` Mario Smarduch [this message]
2015-06-22 3:17 ` Mario Smarduch
2015-06-24 15:44 ` Marc Zyngier
2015-06-24 15:44 ` Marc Zyngier
2015-06-25 3:33 ` Mario Smarduch
2015-06-25 3:33 ` Mario Smarduch
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=55877E42.5070205@samsung.com \
--to=m.smarduch@samsung.com \
--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 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.