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: Wed, 24 Jun 2015 20:33:57 -0700 [thread overview]
Message-ID: <558B76A5.5000308@samsung.com> (raw)
In-Reply-To: <558AD06F.6090103@arm.com>
On 06/24/2015 08:44 AM, Marc Zyngier wrote:
> Hi Mario,
>
> On 19/06/15 19:41, Mario Smarduch wrote:
>> After enhancing arm64 FP/SIMD exit handling, 32-bit VFP exit branch is moved
>> to guest trap handling, keeping exit handling flow for both architectures
>> consistent.
>>
>> Also replaced an unused label with a comment.
>>
>> Signed-off-by: Mario Smarduch <m.smarduch@samsung.com>
>> ---
>> arch/arm/kvm/interrupts.S | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/arch/arm/kvm/interrupts.S b/arch/arm/kvm/interrupts.S
>> index 79caf79..16f00f1 100644
>> --- a/arch/arm/kvm/interrupts.S
>> +++ b/arch/arm/kvm/interrupts.S
>> @@ -363,10 +363,6 @@ hyp_hvc:
>> @ Check syndrome register
>> mrc p15, 4, r1, c5, c2, 0 @ HSR
>> lsr r0, r1, #HSR_EC_SHIFT
>> -#ifdef CONFIG_VFPv3
>> - cmp r0, #HSR_EC_CP_0_13
>> - beq switch_to_guest_vfp
>> -#endif
>> cmp r0, #HSR_EC_HVC
>> bne guest_trap @ Not HVC instr.
>>
>> @@ -380,7 +376,7 @@ hyp_hvc:
>> cmp r2, #0
>> bne guest_trap @ Guest called HVC
>>
>> -host_switch_to_hyp:
>> + /* Guest is calling a hyp function, save minimum context branch to it */
>> 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
>>
>
> Two things: I think you can now drop the load_vcpu that is in
> switch_to_guest_vfp (you just executed it in guest_trap). You also have
> an extra store to VCPU_HSR, but I don't think that's a big deal.
I left VCPU_HSR as is.
- Mario
>
> Thanks,
>
> M.
>
prev parent reply other threads:[~2015-06-25 3:33 UTC|newest]
Thread overview: 4+ 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-22 3:17 ` Mario Smarduch
2015-06-24 15:44 ` Marc Zyngier
2015-06-25 3:33 ` Mario Smarduch [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=558B76A5.5000308@samsung.com \
--to=m.smarduch@samsung.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).