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 X-Spam-Level: X-Spam-Status: No, score=-21.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_GIT, USER_IN_DEF_DKIM_WL autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B0B08C43381 for ; Sat, 13 Feb 2021 00:51:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 944896186A for ; Sat, 13 Feb 2021 00:51:33 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232152AbhBMAvY (ORCPT ); Fri, 12 Feb 2021 19:51:24 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57976 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231743AbhBMAvC (ORCPT ); Fri, 12 Feb 2021 19:51:02 -0500 Received: from mail-qk1-x749.google.com (mail-qk1-x749.google.com [IPv6:2607:f8b0:4864:20::749]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 41BA4C0613D6 for ; Fri, 12 Feb 2021 16:50:22 -0800 (PST) Received: by mail-qk1-x749.google.com with SMTP id v128so995851qkc.12 for ; Fri, 12 Feb 2021 16:50:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=sender:reply-to:date:message-id:mime-version:subject:from:to:cc; bh=B4CJaxKFMc+dqDZ9nbv+QUPSRmvNDPY/ZFqR7df/PF0=; b=fL8hQzokABhTqNEOqbM/Ylp50TCYwNe7DpnzPcHsJQpyHAU76uRAiMCZ2DbbU+FSjW MmlQKPkPEtH8pEGQXpgf1Ei1IYerm5FlXoO9UTRcq7JW9WByA47I8cBVU3uC6+CCVje9 HHyOJyZk4egFJxonkFQDBfdlHUksI5Gg6RVnRMpDYW3r9a4XWsttsNRZy0qsNqoY710T JWkdKnd5tSu5OxtPFfkUXTDAYO7riwxHqiANAgi1Ee6mCgr0VZ32g53B3yxfYmO9kWRO Hr3i4Ljcj3cnRsp89Vfqlom1clZD2Z2Xck32fZZTdjCQ4CUZ0mkKR3/4RLu0m9dqgadi Xh2Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:reply-to:date:message-id:mime-version :subject:from:to:cc; bh=B4CJaxKFMc+dqDZ9nbv+QUPSRmvNDPY/ZFqR7df/PF0=; b=ClUE5zP/U+9g2gS5NyjWtMf0cBBCpuRWgfTehKQ4g4IgNec3+pSolD7to7WMQ/b2SC guvAASJrqBaOBLf/9pWmAyEsfTKVOmo1BkVP3beEaOCKwyJxhrNkKK8TLUzSnqcAc0zS YZEhYgMTAD1oT1HJ5/N8dcoR+DR7+0Lm+xruwW2c6isqMLyMjtF/nJr1iX5XD6PwL1Pt 0Jtu0vqojb4L7KsVX+gHnmJ/a7B63+TDWo1LkVedEXVFVd45MLvXzTurvRSolRZBScKQ HbwBE5JZpAQQR0/uQPfumMTULp+8eeqkfrHd720lfJBTq2RPSO+qd3Oy0khe8ImMUR8P cBXg== X-Gm-Message-State: AOAM532b5gHJtFhCn6xUGWWFE7/1PHORo2d9fWgWiNCirj5DtXPkGL2I wdEmR4430emm77rThi1D4lsJrWOXIws= X-Google-Smtp-Source: ABdhPJyudnIPApIy7Nm66X8yqyeGaOrIdBSvHRVveVNyzL3uEudKmIVxnTmngjCy4IoAK3JPNKBaxaAMohI= Sender: "seanjc via sendgmr" X-Received: from seanjc798194.pdx.corp.google.com ([2620:15c:f:10:b407:1780:13d2:b27]) (user=seanjc job=sendgmr) by 2002:a05:6214:504:: with SMTP id v4mr5165665qvw.58.1613177421259; Fri, 12 Feb 2021 16:50:21 -0800 (PST) Reply-To: Sean Christopherson Date: Fri, 12 Feb 2021 16:50:01 -0800 Message-Id: <20210213005015.1651772-1-seanjc@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.30.0.478.g8a0d178c01-goog Subject: [PATCH 00/14] KVM: x86/mmu: Dirty logging fixes and improvements From: Sean Christopherson To: Paolo Bonzini Cc: Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Ben Gardon , Makarand Sonare Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paolo, this is more or less ready, but on final read-through before sending I realized it would be a good idea to WARN during VM destruction if cpu_dirty_logging_count is non-zero. I wanted to get you this before the 5.12 window opens in case you want the TDP MMU fixes for 5.12. I'll do the above change and retest next week (note, Monday is a US holiday). On to the code... This started out as a small tweak to collapsible SPTE zapping in the TDP MMU, and ended up as a rather large overhaul of CPU dirty logging, a.k.a. PML. Four main highlights: - Do a more precise check on whether or not a SPTE should be zapped to rebuild it as a large page. - Disable PML when running L2. PML is fully emulated for L1 VMMs, thus enabling PML in L2 can only hurt and never help. - Drop the existing PML kvm_x86_ops. They're basically trampolines into the MMU, and IMO do far more harm than good. - Turn on PML only when it's needed instead of setting all dirty bits to soft disable PML. What led me down the rabbit's hole of ripping out the existing PML kvm_x86_ops isn't really shown here. Prior to incorporating Makarand's patch, which allowed for the wholesale remove of setting dirty bits, I spent a bunch of time poking around the "set dirty bits" code. My original changes optimized that path to skip setting dirty bits in the nested MMU, since the nested MMU relies on write-protection and not PML. That in turn allowed the TDP MMU zapping to completely skip walking the rmaps, but doing so based on a bunch of callbacks was a twisted mess. Happily, those patches got dropped in favor of nuking the code entirely. Ran selftest and unit tests, and migrated actual VMs on AMD and Intel, with and without TDP MMU, and with and without EPT. The AMD system I'm testing on infinite loops on the reset vector due to a #PF when NPT is disabled, so that didn't get tested. That reproduces with kvm/next, I'll dig into it next week (no idea if it's a KVM or hardware issue). For actual migration, I ran kvm-unit-tests in L1 along with stress to hammer memory, and verified migration was effectively blocked until the stress threads were killed (I didn't feel like figuring out how to throttle the VM). Makarand Sonare (1): KVM: VMX: Dynamically enable/disable PML based on memslot dirty logging Sean Christopherson (13): KVM: x86/mmu: Expand collapsible SPTE zap for TDP MMU to ZONE_DEVICE pages KVM: x86/mmu: Don't unnecessarily write-protect small pages in TDP MMU KVM: x86/mmu: Split out max mapping level calculation to helper KVM: x86/mmu: Pass the memslot to the rmap callbacks KVM: x86/mmu: Consult max mapping level when zapping collapsible SPTEs KVM: nVMX: Disable PML in hardware when running L2 KVM: x86/mmu: Expand on the comment in kvm_vcpu_ad_need_write_protect() KVM: x86/mmu: Make dirty log size hook (PML) a value, not a function KVM: x86: Move MMU's PML logic to common code KVM: x86: Further clarify the logic and comments for toggling log dirty KVM: x86/mmu: Don't set dirty bits when disabling dirty logging w/ PML KVM: x86: Fold "write-protect large" use case into generic write-protect KVM: x86/mmu: Remove a variety of unnecessary exports arch/x86/include/asm/kvm-x86-ops.h | 6 +- arch/x86/include/asm/kvm_host.h | 36 +---- arch/x86/kvm/mmu/mmu.c | 203 +++++++++-------------------- arch/x86/kvm/mmu/mmu_internal.h | 7 +- arch/x86/kvm/mmu/tdp_mmu.c | 66 +--------- arch/x86/kvm/mmu/tdp_mmu.h | 3 +- arch/x86/kvm/vmx/nested.c | 34 +++-- arch/x86/kvm/vmx/vmx.c | 94 +++++-------- arch/x86/kvm/vmx/vmx.h | 2 + arch/x86/kvm/x86.c | 145 +++++++++++++-------- 10 files changed, 230 insertions(+), 366 deletions(-) -- 2.30.0.478.g8a0d178c01-goog