From: Marc Zyngier <marc.zyngier@arm.com>
To: Bhushan Bharat-R65777 <R65777@freescale.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [PATCH 2/2] arm64: KVM: Yield CPU when vcpu executes a WFE
Date: Mon, 07 Oct 2013 17:00:09 +0100 [thread overview]
Message-ID: <5252DA89.5040605@arm.com> (raw)
In-Reply-To: <6A3DF150A5B70D4F9B66A25E3F7C888D07194569@039-SN2MPN1-011.039d.mgd.msft.net>
On 07/10/13 16:52, Bhushan Bharat-R65777 wrote:
>
>
>> -----Original Message-----
>> From: Marc Zyngier [mailto:marc.zyngier@arm.com]
>> Sent: Monday, October 07, 2013 9:11 PM
>> To: linux-arm-kernel@lists.infradead.org; kvmarm@lists.cs.columbia.edu;
>> kvm@vger.kernel.org
>> Subject: [PATCH 2/2] arm64: KVM: Yield CPU when vcpu executes a WFE
>>
>> On an (even slightly) oversubscribed system, spinlocks are quickly becoming a
>> bottleneck, as some vcpus are spinning, waiting for a lock to be released, while
>> the vcpu holding the lock may not be running at all.
>>
>> The solution is to trap blocking WFEs and tell KVM that we're now spinning. This
>> ensures that other vpus will get a scheduling boost, allowing the lock to be
>> released more quickly.
>>
>> Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
>> ---
>> arch/arm64/include/asm/kvm_arm.h | 8 ++++++--
>> arch/arm64/kvm/handle_exit.c | 18 +++++++++++++-----
>> 2 files changed, 19 insertions(+), 7 deletions(-)
>>
>> diff --git a/arch/arm64/include/asm/kvm_arm.h b/arch/arm64/include/asm/kvm_arm.h
>> index a5f28e2..c98ef47 100644
>> --- a/arch/arm64/include/asm/kvm_arm.h
>> +++ b/arch/arm64/include/asm/kvm_arm.h
>> @@ -63,6 +63,7 @@
>> * TAC: Trap ACTLR
>> * TSC: Trap SMC
>> * TSW: Trap cache operations by set/way
>> + * TWE: Trap WFE
>> * TWI: Trap WFI
>> * TIDCP: Trap L2CTLR/L2ECTLR
>> * BSU_IS: Upgrade barriers to the inner shareable domain
>> @@ -72,8 +73,9 @@
>> * FMO: Override CPSR.F and enable signaling with VF
>> * SWIO: Turn set/way invalidates into set/way clean+invalidate
>> */
>> -#define HCR_GUEST_FLAGS (HCR_TSC | HCR_TSW | HCR_TWI | HCR_VM | HCR_BSU_IS | \
>> - HCR_FB | HCR_TAC | HCR_AMO | HCR_IMO | HCR_FMO | \
>> +#define HCR_GUEST_FLAGS (HCR_TSC | HCR_TSW | HCR_TWE | HCR_TWI | HCR_VM | \
>> + HCR_BSU_IS | HCR_FB | HCR_TAC | \
>> + HCR_AMO | HCR_IMO | HCR_FMO | \
>> HCR_SWIO | HCR_TIDCP | HCR_RW)
>> #define HCR_VIRT_EXCP_MASK (HCR_VA | HCR_VI | HCR_VF)
>>
>> @@ -242,4 +244,6 @@
>>
>> #define ESR_EL2_EC_xABT_xFSR_EXTABT 0x10
>>
>> +#define ESR_EL2_EC_WFI_ISS_WFE (1 << 0)
>
> In another patch this is named as WHI_IS_WFE whereas here it is WFI_ISS_WFE, looks like typo. Anyways, what I am interested to understand is what does this macro means?
Not a typo. It decodes as:
Exception Status Register, Exception Level 2, Exception Class Wait For
Interrupt, Instruction Specific Syndrome Wait For Event.
The ARM code doesn't have such a convention, so I didn't bother. It just
reads "Hyp Status Register, Wait For Interrupt Is Wait For Event".
M.
> Thanks
> -Bharat
>
>> +
>> #endif /* __ARM64_KVM_ARM_H__ */
>> diff --git a/arch/arm64/kvm/handle_exit.c b/arch/arm64/kvm/handle_exit.c index
>> 9beaca03..8da5606 100644
>> --- a/arch/arm64/kvm/handle_exit.c
>> +++ b/arch/arm64/kvm/handle_exit.c
>> @@ -47,21 +47,29 @@ static int handle_smc(struct kvm_vcpu *vcpu, struct kvm_run
>> *run) }
>>
>> /**
>> - * kvm_handle_wfi - handle a wait-for-interrupts instruction executed by a
>> guest
>> + * kvm_handle_wfx - handle a wait-for-interrupts or wait-for-event
>> + * instruction executed by a guest
>> + *
>> * @vcpu: the vcpu pointer
>> *
>> - * Simply call kvm_vcpu_block(), which will halt execution of
>> + * WFE: Yield the CPU and come back to this vcpu when the scheduler
>> + * decides to.
>> + * WFI: Simply call kvm_vcpu_block(), which will halt execution of
>> * world-switches and schedule other host processes until there is an
>> * incoming IRQ or FIQ to the VM.
>> */
>> -static int kvm_handle_wfi(struct kvm_vcpu *vcpu, struct kvm_run *run)
>> +static int kvm_handle_wfx(struct kvm_vcpu *vcpu, struct kvm_run *run)
>> {
>> - kvm_vcpu_block(vcpu);
>> + if (kvm_vcpu_get_hsr(vcpu) & ESR_EL2_EC_WFI_ISS_WFE)
>> + kvm_vcpu_on_spin(vcpu);
>> + else
>> + kvm_vcpu_block(vcpu);
>> +
>> return 1;
>> }
>>
>> static exit_handle_fn arm_exit_handlers[] = {
>> - [ESR_EL2_EC_WFI] = kvm_handle_wfi,
>> + [ESR_EL2_EC_WFI] = kvm_handle_wfx,
>> [ESR_EL2_EC_CP15_32] = kvm_handle_cp15_32,
>> [ESR_EL2_EC_CP15_64] = kvm_handle_cp15_64,
>> [ESR_EL2_EC_CP14_MR] = kvm_handle_cp14_access,
>> --
>> 1.8.2.3
>>
>>
>>
>> _______________________________________________
>> kvmarm mailing list
>> kvmarm@lists.cs.columbia.edu
>> https://lists.cs.columbia.edu/cucslists/listinfo/kvmarm
>
>
>
--
Jazz is not dead. It just smells funny...
prev parent reply other threads:[~2013-10-07 16:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 15:40 [PATCH 0/2] ARM/arm64: KVM: Yield CPU when vcpu executes a WFE Marc Zyngier
2013-10-07 15:40 ` [PATCH 1/2] ARM: " Marc Zyngier
2013-10-07 16:04 ` Alexander Graf
2013-10-07 16:16 ` Marc Zyngier
2013-10-07 16:30 ` Alexander Graf
2013-10-07 16:53 ` Gleb Natapov
2013-10-09 13:09 ` Alexander Graf
2013-10-09 13:26 ` Gleb Natapov
2013-10-09 14:18 ` Marc Zyngier
2013-10-09 14:50 ` Anup Patel
2013-10-09 14:52 ` Anup Patel
2013-10-09 14:59 ` Marc Zyngier
2013-10-09 15:10 ` Anup Patel
2013-10-09 15:17 ` Marc Zyngier
2013-10-09 15:17 ` Anup Patel
2013-10-07 16:55 ` Marc Zyngier
2013-10-08 11:26 ` Raghavendra KT
2013-10-08 12:43 ` Marc Zyngier
2013-10-08 15:02 ` Raghavendra K T
2013-10-08 15:06 ` Marc Zyngier
2013-10-08 15:13 ` Raghavendra K T
2013-10-08 16:09 ` Marc Zyngier
2013-10-07 15:40 ` [PATCH 2/2] arm64: " Marc Zyngier
2013-10-07 15:52 ` Bhushan Bharat-R65777
2013-10-07 16:00 ` Marc Zyngier [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=5252DA89.5040605@arm.com \
--to=marc.zyngier@arm.com \
--cc=R65777@freescale.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--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).