Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp50573rwd; Tue, 6 Jun 2023 18:21:10 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4ZXA6VNCT3B0YltvwUd0Y8hLqzod/0KcZenaX+dTfl3/efme0Rsa74Xa6S0JvNmjf4OjD2 X-Received: by 2002:a05:6a00:238e:b0:64d:1215:a0f5 with SMTP id f14-20020a056a00238e00b0064d1215a0f5mr1666838pfc.34.1686100869765; Tue, 06 Jun 2023 18:21:09 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686100869; cv=none; d=google.com; s=arc-20160816; b=Cv/4sQCg7/gsJKTuo+j3CWY0awpqwPCGkIyo/ipMolarTirn7MsKN7TzuCCLDzMVi+ FWEKr6iFOq4ey8AmFkkz0tUgI+1kwIWcC1CHWN8/NLyEnMobQiQV/MLuDCc7fISaRfwv nYLPycGiJO8xkBfVWV2/MXwWVBuE2097HwTCyeWDcs+qljwuVtckgNQ8iHk8kg1WtGie yDhi6aA4gV2iVkDiKNQi9yoDYUJ6WIasmnFc9Y37sscipRdSK5tDZ6Kn5R8lGyFWu6/8 SkTs92MZ+mSsucPBG4mNBOBGexHZgjMVcHpcsyv8fpLWyqrvCOm9BZLhWcYySO2OnQTY wwaQ== 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:references :mime-version:in-reply-to:date:dkim-signature; bh=TiiO5lm09/llcY60xbB1wTnnlYaNwmcjaEBpMB+pCik=; b=d+YUGQ3bKOTW+Nuw72hWnAX7KW66CRGJeDeIaKkz7uiSjmW1DMPOokoiDpYkYrO4O9 sjbxu3oRlpwt5Jryn+k+N2yhn9Z5KdZ3rCmNV6wDVQd549x2ESQ9BHurksQZwlFEkuXa G3vdzYuZPcHc+Piw1sXKx4SAw+iYV6dILC0bPk95e7/Ps89ZOhclh5bBmxltLVD90ahm WQyFbx+7DhuoX1KgVBa/ADGTIfaAfkLwycOJXyUkYg6A36pY3JtwdgeBYLmqyZBCfXPQ XtgBlrwbiBeVDgRli5Q0sDa+ScXNiTENM4hQ2pY/+S1rPaw+g29mjJmLD0fNoCiBI+hC UW9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20221208 header.b="z/n2Yj8T"; 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 b190-20020a6334c7000000b00528cf858c87si8151285pga.156.2023.06.06.18.20.54; Tue, 06 Jun 2023 18:21:09 -0700 (PDT) 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=20221208 header.b="z/n2Yj8T"; 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 S240390AbjFGAzY (ORCPT + 99 others); Tue, 6 Jun 2023 20:55:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51624 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S240377AbjFGAzN (ORCPT ); Tue, 6 Jun 2023 20:55:13 -0400 Received: from mail-pl1-x649.google.com (mail-pl1-x649.google.com [IPv6:2607:f8b0:4864:20::649]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E19CC19B1 for ; Tue, 6 Jun 2023 17:55:08 -0700 (PDT) Received: by mail-pl1-x649.google.com with SMTP id d9443c01a7336-1b24203569aso2737225ad.2 for ; Tue, 06 Jun 2023 17:55:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1686099308; x=1688691308; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=TiiO5lm09/llcY60xbB1wTnnlYaNwmcjaEBpMB+pCik=; b=z/n2Yj8Ts6rQStJro2tcUg1PikLgoHTBxYJ+XtKESQy+bdryu0EUhVMuvWuMQeHeb8 Ky0hS97SteZuODEwYhAJ+xpUC5n3+1EJ7OWbEJrVJIK+b8hxQd11b1pVTozS+9qvyICg zAGSVT0hYjeXaz6TqE+GCSvnWFfF4LQsfkFt6wxr1lVlRsycMAkWAlgJ3NtLWFlBXHXr PbOetXDr4siY96SThhTxhiJfMVDZR5L+N6G9WQ6Xj929DRbhIb80LBKMkeThO3kz6Vo+ cHMZlowDyM83hiFt85WBD5RH2XjfppX6H9FpEcfgvW0StaH/rd8w3C6QIA+1rLJw+SDK 6aCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1686099308; x=1688691308; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=TiiO5lm09/llcY60xbB1wTnnlYaNwmcjaEBpMB+pCik=; b=gBIO5YdllN+uTWujZJXS1fkaj3angl2nBQFaOMVZDwAAc+ZLYX9SM3xeIVEsZoi9ey qhIH0+v+aXZFPmPEwj6kwjk51Z7uG0oIzuPHeOkONNkk0N8AQSKtp/zVc1KUfw79+fMM oTVDw4vAsyN9gsoaLHsMtag2TpeCusdtZcAQZz95JMSxKZXH9o525DIJR5qsx+SPZZyc Y2cqkD/tzEidUI1I//W6klhp3o0l03gQr65VKC93RwKAlOwd3pU4ETabVs5O/IekU015 9tMc0bH9DpcbWaEyopfxVgIGKKUYnfkEjkkaTKgU8yX3wlSDjGoppN1iPgQyAoG2cERk 0jpQ== X-Gm-Message-State: AC+VfDybGQwlzFv05Gy9fnJMKgYN1Xn06VKyKb3UqqshxSD78dm43EyH 0zRcUGvH8cgkOKLT3Sh1JkOay3poGY8= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a17:902:c20d:b0:1ac:82e8:4917 with SMTP id 13-20020a170902c20d00b001ac82e84917mr1187156pll.13.1686099308332; Tue, 06 Jun 2023 17:55:08 -0700 (PDT) Date: Tue, 6 Jun 2023 17:55:02 -0700 In-Reply-To: <20230602011518.787006-1-seanjc@google.com> Mime-Version: 1.0 References: <20230602011518.787006-1-seanjc@google.com> X-Mailer: git-send-email 2.41.0.162.gfafddb0af9-goog Message-ID: <168608931025.1367101.1539584781892191292.b4-ty@google.com> Subject: Re: [PATCH 0/3] KVM: x86: Use "standard" mmu_notifier hook for APIC page From: Sean Christopherson To: Sean Christopherson , Paolo Bonzini Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Alistair Popple , Robin Murphy , Jason Gunthorpe 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,T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=unavailable 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 On Thu, 01 Jun 2023 18:15:15 -0700, Sean Christopherson wrote: > Convert VMX's handling of mmu_notifier invalidations of the APIC-access page > from invalidate_range() to KVM's standard invalidate_range_{start,end}(). > > KVM (ab)uses invalidate_range() to fudge around not stalling vCPUs until > relevant in-flight invalidations complete. Abusing invalidate_range() works, > but it requires one-off code in KVM, sets a bad precedent in KVM, and is > blocking improvements to mmu_notifier's definition of invalidate_range() > due to KVM's usage diverging wildly from the original intent of notifying > IOMMUs of changes to shared page tables. > > [...] Applied to kvm-x86 vmx, thanks! [1/3] KVM: VMX: Retry APIC-access page reload if invalidation is in-progress https://github.com/kvm-x86/linux/commit/878940b33d76 [2/3] KVM: x86: Use standard mmu_notifier invalidate hooks for APIC access page https://github.com/kvm-x86/linux/commit/0a8a5f2c8c26 [3/3] KVM: x86/mmu: Trigger APIC-access page reload iff vendor code cares https://github.com/kvm-x86/linux/commit/0a3869e14d4a -- https://github.com/kvm-x86/linux/tree/next https://github.com/kvm-x86/linux/tree/fixes