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=-0.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no 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 5684BC2BA83 for ; Sat, 8 Feb 2020 00:18:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1DB4E217BA for ; Sat, 8 Feb 2020 00:18:44 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="O/1W3a8r" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727243AbgBHASn (ORCPT ); Fri, 7 Feb 2020 19:18:43 -0500 Received: from us-smtp-2.mimecast.com ([205.139.110.61]:45362 "EHLO us-smtp-delivery-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1726995AbgBHASn (ORCPT ); Fri, 7 Feb 2020 19:18:43 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1581121119; 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=FliTqS6db2UW8mSq2D177P6p0LFTqK9NtxjpkxKtGhE=; b=O/1W3a8ryKF20gLOZ9d4i4fSs+RrdHctCjc6CcIBMZ2vrlX1RtNbDx8cWE0AsVtnGbxzih CCRbBvG2jmCrPEBBCt2Wg+w2TRMqGuG8RzmqFhV5Nk0MvKdN+hGbJHUqE5Rpuv3whEI0H9 c1rmwxnzyoJSFv+3bYo4uOXOsiinGAA= Received: from mail-qk1-f197.google.com (mail-qk1-f197.google.com [209.85.222.197]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-32-WkX4c1LjNViwqwSZeOmryw-1; Fri, 07 Feb 2020 19:18:37 -0500 X-MC-Unique: WkX4c1LjNViwqwSZeOmryw-1 Received: by mail-qk1-f197.google.com with SMTP id 24so614761qka.16 for ; Fri, 07 Feb 2020 16:18:37 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=FliTqS6db2UW8mSq2D177P6p0LFTqK9NtxjpkxKtGhE=; b=qe3NdTfBeMElNFX3pVkvNHzYvSwLh5t1daWO2kYqbn8QI7fi7TInRwGvB7+1aoZQUo GngT8EdOu61BGcY7Xn7ZqsQ9fush8Bc+IVBeoW/TifGtRIIyBL777HhLcMKqcu7SLLLd uQq1VrTQ8JqjlGx+BJEbxVvzBLh1zCAzcLu2XtzLxP1JljJzRjsPkIf+RCNg6vqt+S2l jZM2jyFyTlt1EBHsUt9xSnXdilzdg8rPkr6PGLJXq3uIm5WIKVa1qy+ID/VBCSGCXlRj brXW5fhnPa1syg35Kl9sbJ74jCBVCeIfu9q1usQ5WIlEtcx6fqqvDvLGJEj/CYtijSWr NW+Q== X-Gm-Message-State: APjAAAVoQ8ZBQnEmCS/TQJbFlH0cV0I+PhaoFza0yAzO2dg20cESiTqU xV9wAp/29k7sxk4BcjoUV0HX3vCe2nzTz7oPF6Kln9Gb4ob2SeCISph+3zjarP43QSDq57m6eBF S+iW3aJjDgThqSEolAgC5zgLt X-Received: by 2002:a37:8cc:: with SMTP id 195mr1462261qki.456.1581121117033; Fri, 07 Feb 2020 16:18:37 -0800 (PST) X-Google-Smtp-Source: APXvYqzAkXLXCBlBGfr3jniMMbcCpWv44CMlkznbhHCioVsTu+8iTId/2cuSvhY/ok33KerrRsEvMw== X-Received: by 2002:a37:8cc:: with SMTP id 195mr1462239qki.456.1581121116707; Fri, 07 Feb 2020 16:18:36 -0800 (PST) Received: from xz-x1 ([2607:9880:19c8:32::2]) by smtp.gmail.com with ESMTPSA id n32sm2271790qtk.66.2020.02.07.16.18.33 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 07 Feb 2020 16:18:35 -0800 (PST) Date: Fri, 7 Feb 2020 19:18:32 -0500 From: Peter Xu To: Sean Christopherson Cc: Vitaly Kuznetsov , Paolo Bonzini , Paul Mackerras , Christian Borntraeger , Janosch Frank , David Hildenbrand , Cornelia Huck , Wanpeng Li , Jim Mattson , Joerg Roedel , Marc Zyngier , James Morse , Julien Thierry , Suzuki K Poulose , linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org, Christoffer Dall , Philippe =?utf-8?Q?Mathieu-Daud=C3=A9?= Subject: Re: [PATCH v5 15/19] KVM: Provide common implementation for generic dirty log functions Message-ID: <20200208001832.GA823968@xz-x1> References: <20200121223157.15263-1-sean.j.christopherson@intel.com> <20200121223157.15263-16-sean.j.christopherson@intel.com> <20200206200200.GC700495@xz-x1> <20200206212120.GF13067@linux.intel.com> <20200206214106.GG700495@xz-x1> <20200207194532.GK2401@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20200207194532.GK2401@linux.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Feb 07, 2020 at 11:45:32AM -0800, Sean Christopherson wrote: > +Vitaly for HyperV > > On Thu, Feb 06, 2020 at 04:41:06PM -0500, Peter Xu wrote: > > On Thu, Feb 06, 2020 at 01:21:20PM -0800, Sean Christopherson wrote: > > > On Thu, Feb 06, 2020 at 03:02:00PM -0500, Peter Xu wrote: > > > > But that matters to this patch because if MIPS can use > > > > kvm_flush_remote_tlbs(), then we probably don't need this > > > > arch-specific hook any more and we can directly call > > > > kvm_flush_remote_tlbs() after sync dirty log when flush==true. > > > > > > Ya, the asid_flush_mask in kvm_vz_flush_shadow_all() is the only thing > > > that prevents calling kvm_flush_remote_tlbs() directly, but I have no > > > clue as to the important of that code. > > > > As said above I think the x86 lockdep is really not necessary, then > > considering MIPS could be the only one that will use the new hook > > introduced in this patch... Shall we figure that out first? > > So I prepped a follow-up patch to make kvm_arch_dirty_log_tlb_flush() a > MIPS-only hook and use kvm_flush_remote_tlbs() directly for arm and x86, > but then I realized x86 *has* a hook to do a precise remote TLB flush. > There's even an existing kvm_flush_remote_tlbs_with_address() call on a > memslot, i.e. this exact scenario. So arguably, x86 should be using the > more precise flush and should keep kvm_arch_dirty_log_tlb_flush(). > > But, the hook is only used when KVM is running as an L1 on top of HyperV, > and I assume dirty logging isn't used much, if at all, for L1 KVM on > HyperV? > > I see three options: > > 1. Make kvm_arch_dirty_log_tlb_flush() MIPS-only and call > kvm_flush_remote_tlbs() directly for arm and x86. Add comments to > explain when an arch should implement kvm_arch_dirty_log_tlb_flush(). > > 2. Change x86 to use kvm_flush_remote_tlbs_with_address() when flushing > a memslot after the dirty log is grabbed by userspace. > > 3. Keep the resulting code as is, but add a comment in x86's > kvm_arch_dirty_log_tlb_flush() to explain why it uses > kvm_flush_remote_tlbs() instead of the with_address() variant. > > I strongly prefer to (2) or (3), but I'll defer to Vitaly as to which of > those is preferable. > > I don't like (1) because (a) it requires more lines code (well comments), > to explain why kvm_flush_remote_tlbs() is the default, and (b) it would > require even more comments, which would be x86-specific in generic KVM, > to explain why x86 doesn't use its with_address() flush, or we'd lost that > info altogether. > I proposed the 4th solution here: https://lore.kernel.org/kvm/20200207223520.735523-1-peterx@redhat.com/ I'm not sure whether that's acceptable, but if it can, then we can drop the kvm_arch_dirty_log_tlb_flush() hook, or even move on to per-slot tlb flushing. Thanks, -- Peter Xu