Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp2182787pxb; Fri, 24 Sep 2021 23:43:24 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzLsngZj0OhEhWWfCmYzyi3naeBEtm3zZ3kZ/UEa7wgpmgAfPlCd68sqrL/yWDhF9HkGW8X X-Received: by 2002:a02:cc21:: with SMTP id o1mr13057824jap.110.1632552203891; Fri, 24 Sep 2021 23:43:23 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1632552203; cv=none; d=google.com; s=arc-20160816; b=PYxe+mIQsdsMnLNkFiXdC+rn1KptBnJQIG7jHKY5L6TSUPYVli/wbtlPInoZJi8x7p ql8JOWyQh/rU3C2K4Ep6bzyQZK5ENzdj7H63YeDndvg8SWZId8yqLLhJL6MwGZFLbj7H H9oQxAv8N4rhXsImrcBZkIpZouNh62l/aqapkogYwP3OHYiNkpNKa9LKY9bg9rYnIDQN VFUx6Do13+A2NzXNQqhE1vtxdzOBLQI8Alvl1xxgrnk5a/hjd0Lvr/MkJVkxHiYym+cY FkTAG6DKPymbR4WxEQyNyZNIwL6HONHASGl1XtsDHPvyMJLPRnVeXTw9aeF/11BH6a6I m4jw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:references:mime-version :message-id:in-reply-to:date:reply-to:dkim-signature; bh=uLdmTcdOYtZZFn/MuvyFluHWXgJOTY2/q4ao2KO0G1s=; b=tJKXLzbDbcAM6x8wtETDVHBcAN5ajlI+lMir37/td5OLa2spz1mCEg8G5DLp++35nJ sM73POKDck0h1suJigX/WPcUV15cAkqNcl7fnpA0I8SV3EFG9pVXzRdb+y97MfW0Jklb OONfzO04Lse5dd5Vx+62BCIFYgQy49axqhBFxvIOxvvvlauqqjIs09GtiWo6Vioxb9zl xAz1yeK8IsjMbNUeWGrSC9sbxigp02c7kApoljQ29NThW3CwjO5uwMnBJxyuOYb3R6os tPD8yIKsbgAR9qZBN+A6aluGZwQSOJd4HAHSlUUIJwfkdDu32IKBkuhAa5ABYfE6uy9j P4NA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=gPL1+MSj; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y15si12942716ilu.118.2021.09.24.23.43.12; Fri, 24 Sep 2021 23:43:23 -0700 (PDT) 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=@google.com header.s=20210112 header.b=gPL1+MSj; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346692AbhIYA5Y (ORCPT + 99 others); Fri, 24 Sep 2021 20:57:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40320 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1346386AbhIYA5Q (ORCPT ); Fri, 24 Sep 2021 20:57:16 -0400 Received: from mail-qt1-x849.google.com (mail-qt1-x849.google.com [IPv6:2607:f8b0:4864:20::849]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 72FA5C06161E for ; Fri, 24 Sep 2021 17:55:42 -0700 (PDT) Received: by mail-qt1-x849.google.com with SMTP id e5-20020ac84905000000b002a69dc43859so41989512qtq.10 for ; Fri, 24 Sep 2021 17:55:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=reply-to:date:in-reply-to:message-id:mime-version:references :subject:from:to:cc; bh=uLdmTcdOYtZZFn/MuvyFluHWXgJOTY2/q4ao2KO0G1s=; b=gPL1+MSjD+xrjkXRcOmwNqC67Mmvr7RuwzpFUcjOcMddzQt5ApvpYmHx9XRbluCLBL Yg1nvCEit3T0YJNXit7IRIoK7VGM0aOPR2LyM5Quj71xnW24SDpghbthAKdIVpkpkzRd X6gkLqVFB0i84k54sjonsicOkdWeYV2sQavG8Mv3aAQIe9i53EotyhPSycXboSC/o/x4 nIX64OghkAl/Sc0vGnSXFuQP7lt0994oRwNLKAlZQBXOCXCEC6YhE0vIEN6r/f82ulAH xcNqf+D9f3lARXxv2SfegpANARLuOHGy1ceCMn8cGGb9ki40BxZxld2KVYTLW7PXUDEk tT2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:reply-to:date:in-reply-to:message-id :mime-version:references:subject:from:to:cc; bh=uLdmTcdOYtZZFn/MuvyFluHWXgJOTY2/q4ao2KO0G1s=; b=1QOqtNoZ2iDZf78jgddbXX8StkW/9H3uwaDO6a43hoGlsTmteIClBBmlhxwU0t2FsQ EfJgzG0zLd5j+OkNEJn1Jt2A6jI4zVXkNbq/JN0t/BQbH2E1VMmb61oF7Pe6zg46cFP5 bxbDvJP6HjUeA9njS4MU2uXR4qJL3qA6rc1wGEAz8vk7pfH7uKVyiu89EGEkky2+BVUp iZ3ZnjvDEnTbAgw4Usgs0Q4TmmXSYjxhuCGCMONYf0DUkFcWmx399aZ6QFDawMjNNNzM FKm3obWPH1PMmq7sSGg6fa+UcmsqQojclLeKMNyuEXbKhVuptIbctEMDDVJ2FO8ylSld Eanw== X-Gm-Message-State: AOAM532XxNDijLOfPaluaw6oTNdbR+XaD2O2YDpyHtfrBHG4FzeLGMm0 GoW8pame3BJahmQkQkpWLGGP8dLq8/c= X-Received: from seanjc798194.pdx.corp.google.com ([2620:15c:90:200:4c72:89be:dba3:2bcb]) (user=seanjc job=sendgmr) by 2002:a05:6214:54f:: with SMTP id ci15mr12992188qvb.29.1632531341625; Fri, 24 Sep 2021 17:55:41 -0700 (PDT) Reply-To: Sean Christopherson Date: Fri, 24 Sep 2021 17:55:19 -0700 In-Reply-To: <20210925005528.1145584-1-seanjc@google.com> Message-Id: <20210925005528.1145584-6-seanjc@google.com> Mime-Version: 1.0 References: <20210925005528.1145584-1-seanjc@google.com> X-Mailer: git-send-email 2.33.0.685.g46640cef36-goog Subject: [PATCH 05/14] KVM: s390: Clear valid_wakeup in kvm_s390_handle_wait(), not in arch hook From: Sean Christopherson To: Marc Zyngier , Huacai Chen , Aleksandar Markovic , Paul Mackerras , Christian Borntraeger , Janosch Frank , Paolo Bonzini Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , David Hildenbrand , Cornelia Huck , Claudio Imbrenda , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linux-kernel@vger.kernel.org, David Matlack , Jing Zhang Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Move the clearing of valid_wakeup out of kvm_arch_vcpu_block_finish() so that a future patch can drop said arch hook. Unlike the other blocking- related arch hooks (vcpu_blocking/unblocking()), vcpu_block_finish() needs to be called even if the KVM doesn't actually block the vCPU. This will allow future patches to differentiate between truly blocking the vCPU and emulating a halt condition without introducing a contradiction. Alternatively, the hook could be renamed to kvm_arch_vcpu_halt_finish(), but there's literally one call site in s390, and future cleanup can also be done to handle valid_wakeup fully within kvm_s390_handle_wait() and allow generic KVM to drop vcpu_valid_wakeup(). No functional change intended. Signed-off-by: Sean Christopherson --- arch/s390/kvm/interrupt.c | 1 + arch/s390/kvm/kvm-s390.c | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/arch/s390/kvm/interrupt.c b/arch/s390/kvm/interrupt.c index 10722455fd02..520450a7956f 100644 --- a/arch/s390/kvm/interrupt.c +++ b/arch/s390/kvm/interrupt.c @@ -1336,6 +1336,7 @@ int kvm_s390_handle_wait(struct kvm_vcpu *vcpu) no_timer: srcu_read_unlock(&vcpu->kvm->srcu, vcpu->srcu_idx); kvm_vcpu_block(vcpu); + vcpu->valid_wakeup = false; __unset_cpu_idle(vcpu); vcpu->srcu_idx = srcu_read_lock(&vcpu->kvm->srcu); diff --git a/arch/s390/kvm/kvm-s390.c b/arch/s390/kvm/kvm-s390.c index 7cabe6778b1b..08ed68639a21 100644 --- a/arch/s390/kvm/kvm-s390.c +++ b/arch/s390/kvm/kvm-s390.c @@ -5082,7 +5082,7 @@ static inline unsigned long nonhyp_mask(int i) void kvm_arch_vcpu_block_finish(struct kvm_vcpu *vcpu) { - vcpu->valid_wakeup = false; + } static int __init kvm_s390_init(void) -- 2.33.0.685.g46640cef36-goog