Received: by 2002:a05:6358:f14:b0:e5:3b68:ec04 with SMTP id b20csp937386rwj; Thu, 22 Dec 2022 17:43:57 -0800 (PST) X-Google-Smtp-Source: AMrXdXuM9mrk1k4ODSEovj/ZVQalcPgmBrSqQpBX0NBpveUBgdDCladanUee0YDS18cg1c0Mf8ez X-Received: by 2002:a17:906:7046:b0:7ae:8194:7e06 with SMTP id r6-20020a170906704600b007ae81947e06mr6621392ejj.56.1671759837755; Thu, 22 Dec 2022 17:43:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1671759837; cv=none; d=google.com; s=arc-20160816; b=RPdGSvBwkgBHRUC4jFJekVqzgnQSJ8nw6gfanvq+yWKwEPlFFIViFFSe2g6XDbInL3 4sS053JK1Vq3EV53t6PqSYWLdZ9fzMAU/1+jyoJml70x6T6HZuANkdlOjvwENedja82T UtRX3QfSyWoKO4AlnA8/VOZ1wk4X3hyrlotNhrIskjtrqbCkB2ZzpRrDvnphukGbj9je 2zSw3+5n6E5kUWoSzDtcjDdTrdTzxHbeY/Dnnr7/vco7eusV2O063Pe91vNIRVExVALk b7umSV8JFjSDTclfGaSepjudDhCefYo1ijz2BhZN+7ch6YSdAIEMwez+4UyFbBhoJW7y 37jg== 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:message-id:mime-version:date :reply-to:dkim-signature; bh=b29o5HSnDYTmWKzTtpaXEeYgrw2TDFKr2p0Q8+HjsNM=; b=YMFO5PrSnI11hPLVL3bGNofeHw0prooyvn3D2sYhY1ZBh5FmoeXIYL3FPpEYaaD0OW bbHudXbJcF9Mp1+CAkfWoqNfNxmlP6wLP7gynCu307sFzllvNMI9RClc8Mj7R/+8rWEU fpt++ZriDbZnLvGz3mKeP5InVCGgqcnAkC5NmTaahXPmYQTIa+SvS3SpueVD4oORDxi1 oVnUsi0El6DVSSLn1qJWXoI0p9IX8aagE8vDq09Zi4DRyKpRPoekglxY8QAxnybzeVAW oStNSyK8tPPHGP+/35HER4VKXQdZgGu1RQk3EdOWB8yLkwtzkLw0fm4stdYZIfa8KhZF NtLg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=ElUFGASv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l20-20020a170906795400b007ad69eba328si1728092ejo.539.2022.12.22.17.43.41; Thu, 22 Dec 2022 17:43:57 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=ElUFGASv; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 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 S230040AbiLWA5t (ORCPT + 69 others); Thu, 22 Dec 2022 19:57:49 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56910 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229506AbiLWA5r (ORCPT ); Thu, 22 Dec 2022 19:57:47 -0500 Received: from mail-pj1-x104a.google.com (mail-pj1-x104a.google.com [IPv6:2607:f8b0:4864:20::104a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D56521892 for ; Thu, 22 Dec 2022 16:57:46 -0800 (PST) Received: by mail-pj1-x104a.google.com with SMTP id r17-20020a17090aa09100b0021903e75f14so1770662pjp.9 for ; Thu, 22 Dec 2022 16:57:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:reply-to:from:to:cc :subject:date:message-id:reply-to; bh=b29o5HSnDYTmWKzTtpaXEeYgrw2TDFKr2p0Q8+HjsNM=; b=ElUFGASvo+SEqmf91jQ7pr4vVjOmXfyFl7KvLXWpDNbxIU5k3lCNmSBWHsYc4izHGT K9reZTzg3Pi/r4XOJJU5+EuAWfrR/NQCZdtaWZN4UuzSAX32pxagnCxgQAKIyqGZl1q5 fInmcehDeJjBJFNRRpgH6ZAXA5DTPoJLacO4DmKKMttX0uFBC9UXy1PpG5QSuh9Vu/QU FNXDe4PQz7L3uuyUHN7Q6TjQJEogC6Fw461JKiT+qo7B1nna606DzaowIs8M33Iho1U6 HtVF8X79gFbB2PPPLE+aK7jxdRtvJZwGkfemnOq/WGU3ktjrHYgjfc1LyUg3h2n1yF7O jWdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:mime-version:date:reply-to :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=b29o5HSnDYTmWKzTtpaXEeYgrw2TDFKr2p0Q8+HjsNM=; b=Xr6MKMldrd2wjkb8L4uHmQtDVA6E/6h1l7iaAwxS9oK00LBy4ekhIL1rGnAHXMbWzG FsML4OgvHAjG4IjwqWdDgjxidkbWRhAIKJUzKjv8hjFvUydq7nMHRwU3LvWr3ynOo9uR eLOIQNIo+NJ41biKQnH09N0Uc529S2bRxfS1xHHyx20zjM4BlzwcV/sRJykXhM5AkrmI AewRrKVchLGrInv5XWUKFvUD6CJGoMfAie6dIQu1lDsPXqzaqhbc76oyjB7s/XOtO9Gj 09WMK8e8znMiM1WcQ4BkyCYQOVIctCZ3QvXyYsQM42vFrmQyx1N5exHzjU9NT1Q5XJne VnDw== X-Gm-Message-State: AFqh2kqQkCVTigH0lHpLJsvGqVOAzlinCXKixKViE85frRlZk+89Enia BphKXIsfo1OUlUqdR7+F/FA7nHyZylk= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:90a:c292:b0:219:828e:ba8 with SMTP id f18-20020a17090ac29200b00219828e0ba8mr927461pjt.118.1671757065401; Thu, 22 Dec 2022 16:57:45 -0800 (PST) Reply-To: Sean Christopherson Date: Fri, 23 Dec 2022 00:57:12 +0000 Mime-Version: 1.0 X-Mailer: git-send-email 2.39.0.314.g84b9a713c41-goog Message-ID: <20221223005739.1295925-1-seanjc@google.com> Subject: [PATCH 00/27] drm/i915/gvt: KVM: KVMGT fixes and page-track cleanups From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini , Zhenyu Wang , Zhi Wang Cc: kvm@vger.kernel.org, intel-gvt-dev@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org, Yan Zhao , Ben Gardon Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Fix a variety of found-by-inspection bugs in KVMGT, and overhaul KVM's page-track APIs to provide a leaner and cleaner interface. The motivation for this series is to (significantly) reduce the number of KVM APIs that KVMGT uses, with a long-term goal of making all kvm_host.h headers KVM-internal. That said, I think the cleanup itself is worthwhile, e.g. KVMGT really shouldn't be touching kvm->mmu_lock. Note! The KVMGT changes are compile tested only as I don't have the necessary hardware (AFAIK). Testing, and lots of it, on the KVMGT side of things is needed and any help on that front would be much appreciated. Sean Christopherson (24): drm/i915/gvt: Verify pfn is "valid" before dereferencing "struct page" KVM: x86/mmu: Factor out helper to get max mapping size of a memslot drm/i915/gvt: Incorporate KVM memslot info into check for 2MiB GTT entry drm/i915/gvt: Verify VFIO-pinned page is THP when shadowing 2M gtt entry drm/i915/gvt: Put the page reference obtained by KVM's gfn_to_pfn() drm/i915/gvt: Don't rely on KVM's gfn_to_pfn() to query possible 2M GTT drm/i915/gvt: Use an "unsigned long" to iterate over memslot gfns drm/i915/gvt: Hoist acquisition of vgpu_lock out to kvmgt_page_track_write() drm/i915/gvt: Protect gfn hash table with dedicated mutex KVM: x86/mmu: Don't rely on page-track mechanism to flush on memslot change KVM: x86/mmu: Don't bounce through page-track mechanism for guest PTEs KVM: drm/i915/gvt: Drop @vcpu from KVM's ->track_write() hook KVM: x86: Reject memslot MOVE operations if KVMGT is attached drm/i915/gvt: Don't bother removing write-protection on to-be-deleted slot KVM: x86/mmu: Move KVM-only page-track declarations to internal header KVM: x86/mmu: Use page-track notifiers iff there are external users KVM: x86/mmu: Drop infrastructure for multiple page-track modes KVM: x86/mmu: Rename page-track APIs to reflect the new reality KVM: x86/mmu: Assert that correct locks are held for page write-tracking KVM: x86/mmu: Bug the VM if write-tracking is used but not enabled KVM: x86/mmu: Drop @slot param from exported/external page-track APIs KVM: x86/mmu: Handle KVM bookkeeping in page-track APIs, not callers KVM: x86/mmu: Add page-track API to query if a gfn is valid drm/i915/gvt: Drop final dependencies on KVM internal details Yan Zhao (3): KVM: x86: Add a new page-track hook to handle memslot deletion drm/i915/gvt: switch from ->track_flush_slot() to ->track_remove_region() KVM: x86: Remove the unused page-track hook track_flush_slot() arch/x86/include/asm/kvm_host.h | 16 +- arch/x86/include/asm/kvm_page_track.h | 67 +++--- arch/x86/kvm/mmu.h | 2 + arch/x86/kvm/mmu/mmu.c | 61 +++--- arch/x86/kvm/mmu/mmu_internal.h | 2 + arch/x86/kvm/mmu/page_track.c | 283 +++++++++++++++----------- arch/x86/kvm/mmu/page_track.h | 59 ++++++ arch/x86/kvm/x86.c | 13 +- drivers/gpu/drm/i915/gvt/gtt.c | 45 ++-- drivers/gpu/drm/i915/gvt/gvt.h | 4 +- drivers/gpu/drm/i915/gvt/kvmgt.c | 138 ++++++------- drivers/gpu/drm/i915/gvt/page_track.c | 10 +- drivers/gpu/drm/i915/gvt/vgpu.c | 1 + 13 files changed, 386 insertions(+), 315 deletions(-) create mode 100644 arch/x86/kvm/mmu/page_track.h base-commit: 9d75a3251adfbcf444681474511b58042a364863 -- 2.39.0.314.g84b9a713c41-goog