Received: by 2002:a05:6a10:8395:0:0:0:0 with SMTP id n21csp668558pxh; Wed, 10 Nov 2021 07:40:00 -0800 (PST) X-Google-Smtp-Source: ABdhPJwfnXvhIUY7AOxGJh1NfjZK1mEzkm1z3oDfJKnHNB1AeO4SS/Xu9EGyQPT0clZwb5u/M9cu X-Received: by 2002:a17:906:780a:: with SMTP id u10mr310ejm.235.1636558800359; Wed, 10 Nov 2021 07:40:00 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1636558800; cv=none; d=google.com; s=arc-20160816; b=JLvgowYMK36K9cVM6S3yLFEh6Ab/IQXi9zfKqm+wP2q90Pf78qulLX4B8Bn/LToG/u RTbFuo5B+GYkJK5Fy/YeJU7iJS2wb2YIEdF5wFxCJQXUqrRvRU80LdoT1KVl+UtCXJS0 HTMBCr72xMmeCD/JlQ1/sPMKEgm38pyEOoQ2guJre9NI6sewQt4JuZ5qGy3tlS/0bdoT yhtqim88qYL5ldNcNhjkwXuFIOIkURR3LnL4lwSC/ChMhBs2sUVqAfCfL7U6nuFNhaeD ICQhhLhGevJxukcinzEtFvBClxtc7P+NZbCmILOjJ1Bdv19b7ag4BnNlvPITPZvCGuAT Geog== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=TsMK8Ym36EtrROun3gA7xiKiYj4bqI5P7kgHHKBVFyA=; b=TEJmmITrUz5/96Tm8mFwdSrmwuIZWtySTJdWOllVITkWauCjuZVz4tN4AuY5YcAs/k xYHGLLOMpDwG1gK6uMYwnaAgaIkgG0Mn8yNjpWbgguXZlFKGeRiYHnkke59v4XGeyCqH 101S22SzuLizBZLiRndASiX1tIPwXib5cGQVFfPDEU/p6iiLKNleEWUIQM5tiRXRLrWh oqxZIeW+6T7qTRhnARjGCpbBzXknltxD08VEism/lGA5bp7WEOnIxejMO/taQyNuqL2d Y67jaL63XyE2csjBA9lhax1TgJXOBjVSQGvoUpvqQJG5pz+QKkYjDWsg5P9IMgTsK/gS +Z9Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=D6+xZiYl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id sa24si514616ejc.312.2021.11.10.07.39.24; Wed, 10 Nov 2021 07:40:00 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=D6+xZiYl; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232434AbhKJPkA (ORCPT + 99 others); Wed, 10 Nov 2021 10:40:00 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:45046 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231408AbhKJPj7 (ORCPT ); Wed, 10 Nov 2021 10:39:59 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1636558631; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=TsMK8Ym36EtrROun3gA7xiKiYj4bqI5P7kgHHKBVFyA=; b=D6+xZiYlf5a/kWyUzRdJbYXH5SjHYm7zu22ObyIdochIYGdTX6zIabrC3T+iqKwfKoV+D1 UBHAkmOzLEKMXzixZd3WFgH9EF0dVCFBBzEtZ+FBFfppeoYtfga4kpdlI1uUGiS2KXKXza iUo9hAIh8ZTpanW4xhFuT+/10mdSvxA= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-395-1BbL__crP1KCcCERRxfqog-1; Wed, 10 Nov 2021 10:37:09 -0500 X-MC-Unique: 1BbL__crP1KCcCERRxfqog-1 Received: by mail-wr1-f69.google.com with SMTP id h7-20020adfaa87000000b001885269a937so503119wrc.17 for ; Wed, 10 Nov 2021 07:37:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=TsMK8Ym36EtrROun3gA7xiKiYj4bqI5P7kgHHKBVFyA=; b=ND9De0Ew5ZV9hxlXLnNAxHgj3e29TsCwKqQFvizo+EGAj9nLpGAjgSMZrxsY680lXE 5z5mOGXOlkrXiw3qaGi79DurkIhMmeoJV2jLHh+qREM4lak9eN6TxA4QFkAAWBfr+fWm YgfUxyc9ClFD14I3b0IlgskDVMQGaJc0zvafNmc+YhMeg3Lvpi4wKEHoNVNxgi5lDXOZ 2nWiaqQyfYnA6C6qla++auISLW1j78AqVupdpY3i4K7JkwP6LWEgbQgZNWxHuZAZXdO+ 1D78HHBQgTv2i+tFH3OZzPPpOoa+J2ysAcZs4z0wpxzFTXImfp0V9yjiSfvbwbd+Lex/ 21Fw== X-Gm-Message-State: AOAM532y+6068yRd+hyclu00yNCmqmPwzRoKCu0Fz0WrRFQdA7VButGS MpKMEB18mGCXxeHhmtigjvCnZ5r4qqMLan3aGTdrhB2ceHIEbB7KuRFt/w6UQvzq2B4qgMlcXWM 2BzVWn5kjlkRY19dxRBEAAxDA X-Received: by 2002:a5d:6501:: with SMTP id x1mr747759wru.390.1636558625622; Wed, 10 Nov 2021 07:37:05 -0800 (PST) X-Received: by 2002:a5d:6501:: with SMTP id x1mr747721wru.390.1636558625424; Wed, 10 Nov 2021 07:37:05 -0800 (PST) Received: from ?IPv6:2a01:e0a:59e:9d80:527b:9dff:feef:3874? ([2a01:e0a:59e:9d80:527b:9dff:feef:3874]) by smtp.gmail.com with ESMTPSA id n32sm6983581wms.1.2021.11.10.07.37.04 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 10 Nov 2021 07:37:04 -0800 (PST) Subject: Re: [PATCH v4 02/15] KVM: async_pf: Add helper function to check completion queue To: Gavin Shan , kvmarm@lists.cs.columbia.edu Cc: kvm@vger.kernel.org, maz@kernel.org, linux-kernel@vger.kernel.org, shan.gavin@gmail.com, Jonathan.Cameron@huawei.com, pbonzini@redhat.com, vkuznets@redhat.com, will@kernel.org References: <20210815005947.83699-1-gshan@redhat.com> <20210815005947.83699-3-gshan@redhat.com> From: Eric Auger Message-ID: <56d8dbec-a8fd-b109-0c0f-b01c1aef4741@redhat.com> Date: Wed, 10 Nov 2021 16:37:03 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <20210815005947.83699-3-gshan@redhat.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Gavin, On 8/15/21 2:59 AM, Gavin Shan wrote: > This adds inline helper kvm_check_async_pf_completion_queue() to > check if there are pending completion in the queue. The empty stub > is also added on !CONFIG_KVM_ASYNC_PF so that the caller needn't > consider if CONFIG_KVM_ASYNC_PF is enabled. > > All checks on the completion queue is done by the newly added inline > function since list_empty() and list_empty_careful() are interchangeable. why is it interchangeable? > > Signed-off-by: Gavin Shan > --- > arch/x86/kvm/x86.c | 2 +- > include/linux/kvm_host.h | 10 ++++++++++ > virt/kvm/async_pf.c | 10 +++++----- > virt/kvm/kvm_main.c | 4 +--- > 4 files changed, 17 insertions(+), 9 deletions(-) > > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > index e5d5c5ed7dd4..7f35d9324b99 100644 > --- a/arch/x86/kvm/x86.c > +++ b/arch/x86/kvm/x86.c > @@ -11591,7 +11591,7 @@ static inline bool kvm_guest_apic_has_interrupt(struct kvm_vcpu *vcpu) > > static inline bool kvm_vcpu_has_events(struct kvm_vcpu *vcpu) > { > - if (!list_empty_careful(&vcpu->async_pf.done)) > + if (kvm_check_async_pf_completion_queue(vcpu)) > return true; > > if (kvm_apic_has_events(vcpu)) > diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h > index 85b61a456f1c..a5f990f6dc35 100644 > --- a/include/linux/kvm_host.h > +++ b/include/linux/kvm_host.h > @@ -339,12 +339,22 @@ struct kvm_async_pf { > bool notpresent_injected; > }; > > +static inline bool kvm_check_async_pf_completion_queue(struct kvm_vcpu *vcpu) > +{ > + return !list_empty_careful(&vcpu->async_pf.done); > +} > + > void kvm_clear_async_pf_completion_queue(struct kvm_vcpu *vcpu); > void kvm_check_async_pf_completion(struct kvm_vcpu *vcpu); > bool kvm_setup_async_pf(struct kvm_vcpu *vcpu, gpa_t cr2_or_gpa, > unsigned long hva, struct kvm_arch_async_pf *arch); > int kvm_async_pf_wakeup_all(struct kvm_vcpu *vcpu); > #else > +static inline bool kvm_check_async_pf_completion_queue(struct kvm_vcpu *vcpu) > +{ > + return false; > +} > + > static inline void kvm_check_async_pf_completion(struct kvm_vcpu *vcpu) { } > #endif > > diff --git a/virt/kvm/async_pf.c b/virt/kvm/async_pf.c > index dd777688d14a..d145a61a046a 100644 > --- a/virt/kvm/async_pf.c > +++ b/virt/kvm/async_pf.c > @@ -70,7 +70,7 @@ static void async_pf_execute(struct work_struct *work) > kvm_arch_async_page_present(vcpu, apf); > > spin_lock(&vcpu->async_pf.lock); > - first = list_empty(&vcpu->async_pf.done); > + first = !kvm_check_async_pf_completion_queue(vcpu); > list_add_tail(&apf->link, &vcpu->async_pf.done); > apf->vcpu = NULL; > spin_unlock(&vcpu->async_pf.lock); > @@ -122,7 +122,7 @@ void kvm_clear_async_pf_completion_queue(struct kvm_vcpu *vcpu) > spin_lock(&vcpu->async_pf.lock); > } > > - while (!list_empty(&vcpu->async_pf.done)) { > + while (kvm_check_async_pf_completion_queue(vcpu)) { this is replaced by a stronger check. Please can you explain why is it equivalent? > struct kvm_async_pf *work = > list_first_entry(&vcpu->async_pf.done, > typeof(*work), link); > @@ -138,7 +138,7 @@ void kvm_check_async_pf_completion(struct kvm_vcpu *vcpu) > { > struct kvm_async_pf *work; > > - while (!list_empty_careful(&vcpu->async_pf.done) && > + while (kvm_check_async_pf_completion_queue(vcpu) && > kvm_arch_can_dequeue_async_page_present(vcpu)) { > spin_lock(&vcpu->async_pf.lock); > work = list_first_entry(&vcpu->async_pf.done, typeof(*work), > @@ -205,7 +205,7 @@ int kvm_async_pf_wakeup_all(struct kvm_vcpu *vcpu) > struct kvm_async_pf *work; > bool first; > > - if (!list_empty_careful(&vcpu->async_pf.done)) > + if (kvm_check_async_pf_completion_queue(vcpu)) > return 0; > > work = kmem_cache_zalloc(async_pf_cache, GFP_ATOMIC); > @@ -216,7 +216,7 @@ int kvm_async_pf_wakeup_all(struct kvm_vcpu *vcpu) > INIT_LIST_HEAD(&work->queue); /* for list_del to work */ > > spin_lock(&vcpu->async_pf.lock); > - first = list_empty(&vcpu->async_pf.done); > + first = !kvm_check_async_pf_completion_queue(vcpu); > list_add_tail(&work->link, &vcpu->async_pf.done); > spin_unlock(&vcpu->async_pf.lock); > > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index b50dbe269f4b..8795503651b1 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -3282,10 +3282,8 @@ static bool vcpu_dy_runnable(struct kvm_vcpu *vcpu) > if (kvm_arch_dy_runnable(vcpu)) > return true; > > -#ifdef CONFIG_KVM_ASYNC_PF > - if (!list_empty_careful(&vcpu->async_pf.done)) > + if (kvm_check_async_pf_completion_queue(vcpu)) > return true; > -#endif > > return false; > } > Thanks Eric