Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp603130pxj; Thu, 10 Jun 2021 08:20:31 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxA99BWja+5c64KTjNpspHKsnBwAVKPzx3quR6PEIynz+a82G5qwfnK7lyWroc2hVqhJP0W X-Received: by 2002:a17:906:b34e:: with SMTP id cd14mr113008ejb.69.1623338431208; Thu, 10 Jun 2021 08:20:31 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623338431; cv=none; d=google.com; s=arc-20160816; b=iHkOlRerS2Yl3ngy2VqzCkcllbXmJVAR7eLlmHwWI7AHklldfAm219dqHMsHlWI6ps rOl0joxNkPaXdI4+TC6WJGN0P9TWtotEPHrEXr8zsYvR6ovjhtL0o6cv/p7iXX7lro3g PSlo3e76oXOXSr1bsY0nii4bMTLh9SzznKkMjDay/R+I7yRBCBDaNhWReFMLQkoGYJrT AJLGbLBJPkrAXsLxtuwSu/q5F0EGRL+oo21l5bwim7K+g0SGfetpFyi7bcVPhw5ejcaq X9eh1FSvFS9WWYt/HIa3V2188/rTKfeQCRA3U2FIosnk4OoNHNGYJGqCiK9iVc016ogv usZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature; bh=uvvlZU+GigwYDe2gW41VAVg7tPYfG2cr//m/IuHGiJY=; b=AAaepdnqeAMYVIBHLgfGv1ivbKrecF+n9Vvkw6qZjAv+eussA8xMQ3VtM4n8kGfcfG rhi+o3Dwq92bnMR7GndrKXS97E+naxF27Z1jVLI9d+JYozGAU4t6qnoiFD9/nWHhGrk3 rQFgMNVuiC4k58JYHnpFiR6lFhZiD8fEYxZO3U2Al1HlbaaSc3rVl3yyqck4z3a7hmE/ NFMlFbTs6pSTO3cIssGg19UIchKgRkIWr9YZkWKD9ge/iflVTFEQw3RoRv9fTBV6YhHR 9EZhraEarunACR6xHCOZ2zrR2IGfcPeUQ01VveeXc8xPBA3AoVmMJAcvjBdTFh5K4MnI W0Sw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Xq7QKjgA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c7si2371961ejz.386.2021.06.10.08.20.07; Thu, 10 Jun 2021 08:20:31 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Xq7QKjgA; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230287AbhFJPS6 (ORCPT + 99 others); Thu, 10 Jun 2021 11:18:58 -0400 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:27083 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231451AbhFJPS5 (ORCPT ); Thu, 10 Jun 2021 11:18:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623338220; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=uvvlZU+GigwYDe2gW41VAVg7tPYfG2cr//m/IuHGiJY=; b=Xq7QKjgAi6cOuOcjxhZ4bhrFjSG5XEHAk+G2HQy1p/AAXWFOvaQYo6nsYImLEQNzMlofL5 w+LSoDTlvHakzmNVDikTSfXMt1OVbNuh8bGF4rsEVi+pbkPJx4GGCivmTc5yNIGu1xCcuq OARf3e5qwxrVEzWOTqJPUVg6DPuAF28= Received: from mail-wm1-f72.google.com (mail-wm1-f72.google.com [209.85.128.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-203-xvyWKFcPNmykxAZgSQJHjA-1; Thu, 10 Jun 2021 11:16:59 -0400 X-MC-Unique: xvyWKFcPNmykxAZgSQJHjA-1 Received: by mail-wm1-f72.google.com with SMTP id a19-20020a1c98130000b02901960b3b5621so1249578wme.8 for ; Thu, 10 Jun 2021 08:16:59 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=uvvlZU+GigwYDe2gW41VAVg7tPYfG2cr//m/IuHGiJY=; b=gvTnaW1SGFQ42B7gXC+W17+7TR+CIHbIjBKj3s35MGxzmhz9K38Pmn8TnwMCg/cYNU Iinbt1oMYXQORgguvVD9+0I6K+0BKYAGVQtrY2TkdOk2Mwaj7uZsueNVTxBdngWf1iRC Rx7wu1dbu38Dq7KcOCqxAzHJiuaCQXAFR1DxKJPPKB48DfXFqhy/ViK67CryWrpoQXGy sf1Eh98/9O0ZdIj3wHUwF9F4xL0sUbSh4M8gxWW4T7zuMtqG7ZMqwLW8VM4Q3a6RzaXv ZuIh2lZBHxgYQNbjqglX/zHKJ0t16RgBDdvLFQIj+CKvu6QDERr8WHjG+xAxg76GeBP2 9Yig== X-Gm-Message-State: AOAM531esytAj7kY6YTvvFIvzWT9fzDopkx+JfywmD0UjsNDUE1jGLHs RH/0hUJDsXPq0nX/Yw8/IKxqS/T0K8BN8SaqYMrGsXkpmtwYKRPs7o68eOv9eaVS3e/qf6Ph9wm Yh0gaI2++ensQIGBWokUEQ3Kn X-Received: by 2002:a1c:1fc8:: with SMTP id f191mr3963422wmf.33.1623338218397; Thu, 10 Jun 2021 08:16:58 -0700 (PDT) X-Received: by 2002:a1c:1fc8:: with SMTP id f191mr3963407wmf.33.1623338218245; Thu, 10 Jun 2021 08:16:58 -0700 (PDT) Received: from ?IPv6:2001:b07:add:ec09:c399:bc87:7b6c:fb2a? ([2001:b07:add:ec09:c399:bc87:7b6c:fb2a]) by smtp.gmail.com with ESMTPSA id o9sm3587454wri.68.2021.06.10.08.16.56 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 10 Jun 2021 08:16:57 -0700 (PDT) Subject: Re: [PATCH v5 7/7] KVM: SVM: hyper-v: Direct Virtual Flush support To: Vitaly Kuznetsov , Vineeth Pillai Cc: "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "K. Y. Srinivasan" , x86@kernel.org, kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-hyperv@vger.kernel.org, Lan Tianyu , Michael Kelley , Sean Christopherson , Tom Lendacky , Wanpeng Li , Jim Mattson , Joerg Roedel , Wei Liu , Stephen Hemminger , Haiyang Zhang References: <871r9aynoe.fsf@vitty.brq.redhat.com> From: Paolo Bonzini Message-ID: Date: Thu, 10 Jun 2021 17:16:55 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: <871r9aynoe.fsf@vitty.brq.redhat.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/06/21 13:16, Vitaly Kuznetsov wrote: >> +int hv_enable_direct_tlbflush(struct kvm_vcpu *vcpu) >> +{ > I would've avoided re-using 'hv_enable_direct_tlbflush()' name which we > already have in vmx. In fact, in the spirit of this patch, I'd suggest > we create arch/x86/kvm/vmx/vmx_onhyperv.c and move the existing > hv_enable_direct_tlbflush() there. We can then re-name it to e.g. > > vmx_enable_hv_direct_tlbflush() > > so the one introduced by this patch will be > > svm_enable_hv_direct_tlbflush() > I did the rename, and agree with creating a similar file that is split off vmx.c. Paolo