All of lore.kernel.org
 help / color / mirror / Atom feed
From: "chenxiang (M)" <chenxiang66@hisilicon.com>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: <maz@kernel.org>, <james.morse@arm.com>, <kvmarm@lists.linux.dev>,
	<kvm@vger.kernel.org>, <linuxarm@huawei.com>
Subject: Re: [PATCH] KVM: arm64: Keep need_db always true in vgic_v4_put() when emulating WFI
Date: Mon, 10 Jul 2023 10:04:24 +0800	[thread overview]
Message-ID: <24c130cd-b4ac-de18-770e-8495acd41114@hisilicon.com> (raw)
In-Reply-To: <ZKhIXFlPykpvI8MG@linux.dev>

Hi Oliver,


在 2023/7/8 星期六 1:16, Oliver Upton 写道:
> Hi Xiang,
>
> Thanks for reporting this.
>
> On Fri, Jul 07, 2023 at 04:55:45PM +0800, chenxiang wrote:
>> When enabled GICv4.1 on Kunpeng 920 platform with 6.4 kernel (preemptible
>> kernel), running a vm with 128 vcpus on 64 pcpu, sometimes vm is not booted
>> successfully, and we find there is a situation that doorbell interrupt will
>> not occur event if there is a pending interrupt.
> Oh, that's no good.
>
>> ---
>>   arch/arm64/kvm/vgic/vgic-v4.c | 3 +++
>>   1 file changed, 3 insertions(+)
>>
>> diff --git a/arch/arm64/kvm/vgic/vgic-v4.c b/arch/arm64/kvm/vgic/vgic-v4.c
>> index c1c28fe..37152cf8 100644
>> --- a/arch/arm64/kvm/vgic/vgic-v4.c
>> +++ b/arch/arm64/kvm/vgic/vgic-v4.c
>> @@ -343,6 +343,9 @@ int vgic_v4_put(struct kvm_vcpu *vcpu, bool need_db)
>>   	if (!vgic_supports_direct_msis(vcpu->kvm) || !vpe->resident)
>>   		return 0;
>>   
>> +	if (vcpu->stat.generic.blocking == 1)
>> +		need_db = true;
>> +
> As I understand it, the issue really comes from the fact that @need_db
> is always false when called from vgic_v3_put(). I'd rather we not
> override the argument, as that could have unintended consequences in the
> future.
>
> You could also use the helper we already have for determining if a vCPU
> is blocking, which we could use as a hint for requesting a doorbell
> interrupt on sched out.
>
> Putting the two comments together, I arrived at the following (untested)
> diff. I don't have a GICv4 system on hand, sadly. Mind taking it for a
> spin?

Right, it is more suitable to use the helper we already have for 
determining if a vCPU is blocking.
We have tested the following diff you provide, and it solves the issue, 
so please feel free to add for the change:
Tested-by: Xiang Chen <chenxiang66@hisilicon.com>


>
> --
> Thanks,
> Oliver
>
> diff --git a/arch/arm64/kvm/vgic/vgic-v3.c b/arch/arm64/kvm/vgic/vgic-v3.c
> index 93a47a515c13..8c743643b122 100644
> --- a/arch/arm64/kvm/vgic/vgic-v3.c
> +++ b/arch/arm64/kvm/vgic/vgic-v3.c
> @@ -756,7 +756,7 @@ void vgic_v3_put(struct kvm_vcpu *vcpu)
>   {
>   	struct vgic_v3_cpu_if *cpu_if = &vcpu->arch.vgic_cpu.vgic_v3;
>   
> -	WARN_ON(vgic_v4_put(vcpu, false));
> +	WARN_ON(vgic_v4_put(vcpu, kvm_vcpu_is_blocking(vcpu)));
>   
>   	vgic_v3_vmcr_sync(vcpu);
>   
> .
>


      reply	other threads:[~2023-07-10  2:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-07  8:55 [PATCH] KVM: arm64: Keep need_db always true in vgic_v4_put() when emulating WFI chenxiang
2023-07-07 17:16 ` Oliver Upton
2023-07-10  2:04   ` chenxiang (M) [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=24c130cd-b4ac-de18-770e-8495acd41114@hisilicon.com \
    --to=chenxiang66@hisilicon.com \
    --cc=james.morse@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linuxarm@huawei.com \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    /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.