From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 1C31EC433EF for ; Fri, 25 Mar 2022 10:38:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1358921AbiCYKkH (ORCPT ); Fri, 25 Mar 2022 06:40:07 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51958 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1351631AbiCYKkB (ORCPT ); Fri, 25 Mar 2022 06:40:01 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id C789666637 for ; Fri, 25 Mar 2022 03:38:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1648204705; 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: in-reply-to:in-reply-to:references:references; bh=k8Ww1TQL/x1udfrBe7ulqa+UDnc+QUOwf2wvM/b+uX8=; b=VOYIqzgibAQoa7cn6YEyNMjko28wnZo9bPkI/vQlBYwGunGbB2BrmaIbqSbzgC6rHDqLxA 0eiBmaKxEuvJ66OwkgUlJHOTtHCUBcOSkqg8GiP7PXOzPMhaBFBRAhBlwqGWd47h2qZFq4 XdYf55mZSwSJi8Vp+dw/DOsOIDpi+0k= Received: from mail-wm1-f70.google.com (mail-wm1-f70.google.com [209.85.128.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-426-N1ENZm-RO_ebOIIvhQ90xw-1; Fri, 25 Mar 2022 06:38:24 -0400 X-MC-Unique: N1ENZm-RO_ebOIIvhQ90xw-1 Received: by mail-wm1-f70.google.com with SMTP id v2-20020a05600c214200b0038c7c02deceso2551050wml.8 for ; Fri, 25 Mar 2022 03:38:24 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:in-reply-to:references:date :message-id:mime-version; bh=k8Ww1TQL/x1udfrBe7ulqa+UDnc+QUOwf2wvM/b+uX8=; b=YQNPiXAtPtbwlWPe70bWCZvkCmG3p0ExlC1MEsMA+QcNcyjSBACaaMixd8FGrEqhnj 6wC/t0akyvXe3YWWJTHOqo6WLRQFuYxWWdrMKISR+LZGOMf1HsEkSi/cZ8tGnbCiz8FI Np+3LbTm6/Alghc0O8C1uAhFOaI2cHlbe8ZhfIX8IHwH+r9A+izo5TDP6in16FlFyfIk WhpI1tiavbQDNyk9XN6ohoSMZuxc5Zjsz1YJv9nEhKb4+0qswkcsPphvErEEjNhH2RfO arQFiw80VlPLC4WsNxPA5vdSmYhXYAI4FYkiAw+DdaR0A6gzEXLC7GYKrCzbM7qI+WB5 A5jQ== X-Gm-Message-State: AOAM532X7he8NfZFSAlRv1NDE79guuIkNF81TtWQk/zpRb2v7mbStA6Y LhEE/gCFVgGD8S7Momura0uEBpiQxvkTbtEPCUeYxaqU/vqr46BWNzRZdb9MI1PaVU2MkwK1fXR BH6YR9gn/l5LJd0owwayHbwzz X-Received: by 2002:a1c:ed01:0:b0:38b:5a39:220c with SMTP id l1-20020a1ced01000000b0038b5a39220cmr18244095wmh.167.1648204703467; Fri, 25 Mar 2022 03:38:23 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyMj734PZyhmluPDLs9xmQ6pJD2H5U4RSrOcVOm06J/lWrAktgKtttWoMVSaRs+Ejoq5YeU5A== X-Received: by 2002:a1c:ed01:0:b0:38b:5a39:220c with SMTP id l1-20020a1ced01000000b0038b5a39220cmr18244075wmh.167.1648204703249; Fri, 25 Mar 2022 03:38:23 -0700 (PDT) Received: from fedora (nat-2.ign.cz. [91.219.240.2]) by smtp.gmail.com with ESMTPSA id q11-20020adfcd8b000000b001e320028660sm4551557wrj.92.2022.03.25.03.38.22 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Mar 2022 03:38:22 -0700 (PDT) From: Vitaly Kuznetsov To: Sean Christopherson Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Sean Christopherson , Paolo Bonzini Subject: Re: [FYI PATCH] Revert "KVM: x86/mmu: Zap only TDP MMU leafs in kvm_zap_gfn_range()" In-Reply-To: References: <20220318164833.2745138-1-pbonzini@redhat.com> Date: Fri, 25 Mar 2022 11:38:21 +0100 Message-ID: <87tubmnwpu.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Sean Christopherson writes: > On Mon, Mar 21, 2022, Paolo Bonzini wrote: >> On 3/18/22 17:48, Paolo Bonzini wrote: >> > This reverts commit cf3e26427c08ad9015956293ab389004ac6a338e. >> > >> > Multi-vCPU Hyper-V guests started crashing randomly on boot with the >> > latest kvm/queue and the problem can be bisected the problem to this >> > particular patch. ... > > Vitaly, can you provide repro instructions? A nearly-complete QEMU command line > would be wonderful :-) The issue was observed with genuine Hyper-V guests, with or without any Hyper-V enlightenments (not with Linux using Hyper-V enlightenments) The QEMU command line is nothing special, e.g. ~/qemu/build/qemu-system-x86_64 -machine q35,accel=kvm,kernel-irqchip=split -name guest=win2019 -cpu host -smp 16 -m 16384 -drive file=/home/VMs/ws2019_gen1.qcow2,format=qcow2,if=none,id=drive-ide0-0-0 -device ide-hd,bus=ide.0,unit=0,drive=drive-ide0-0-0,id=ide0-0-0,bootindex=1 -vnc :0 -rtc base=localtime,driftfix=slew --no-hpet -monitor stdio --no-reboot I'm also pretty sure I saw this on both AMD and Intel hosts, I can try reproducing if needed. -- Vitaly