Received: by 2002:a9a:4c47:0:b029:116:c383:538 with SMTP id u7csp828604lko; Tue, 13 Jul 2021 11:01:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxGkyII7ndgT8xaT+GlN96D94goF4aQyYiHwU7O4hbMIVE9J4u8eFZcoUEFQvTj/1rDRgkB X-Received: by 2002:a05:6402:1118:: with SMTP id u24mr7400213edv.229.1626199302609; Tue, 13 Jul 2021 11:01:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626199302; cv=none; d=google.com; s=arc-20160816; b=VAy0YX8qM/EzNpBoH6PopeCKTiEmYAaALdY3bJU5DIgoa9NE+JktrGUD9G0F/hLdP3 sHEloPF4ghGlWj3V2Q8CH/Dxet63DqJTgP5vVtzP96OjOEM0GrqpUuPiUXdSh7nm9zQ0 Z/VJiFWQkROWocDZd4DMXLThya3Z4eO6cE/kdiSB+N1XgohPDr8UBBBQkNL7HPvJfRJp dARgsCMH81VEiZhWs6cYNkgU87jgZ3p1+8Cj98KNBhp6r3Qd0H6b81VnMaVar8XRht2h z+Tw2YNcLmowd40vN9adTb+oJLRCqmotTN1xXCSyO66fPF2lHT+44KvgwFzgsjAkDBsy gt0w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=aUnwvzo3iJx64EYOs36puVhqp9GJq4422krM2Lg28ME=; b=IwfRpPErZeDEpx12lECJAH4aCooqaQJfIsDkhgFxYAFaCqMyGvubuDh9CSeANFggn3 HMjCt+0S7Flbg/b1NyUlRHPQiJpK4WIgKfB/f3TUGdJToCRQQUQJnd0ONBiy2yd0+VQ3 hZQvnVkrG5MBogdESXvsU7rnMEmrSO2QA8lVn2PnT+lun9zuv19vwoihWKXe7nwANAgS Ip2odXsaLToigABIZWLQXQUrlu/K6ukj1RupTr696yZ2bipp/6ImEyMuyBllzo2FuVL5 zWmfnM3+0CPJT3OwjhiayI7czFaqEFbCcoKhEDB+Q5YKfCNze7Uw+Og6NMeFbRzG788L sdhw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=pjVheK0z; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i22si6750343ejh.547.2021.07.13.11.01.18; Tue, 13 Jul 2021 11:01:42 -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=@google.com header.s=20161025 header.b=pjVheK0z; 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=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232455AbhGMSDC (ORCPT + 99 others); Tue, 13 Jul 2021 14:03:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36778 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229478AbhGMSDA (ORCPT ); Tue, 13 Jul 2021 14:03:00 -0400 Received: from mail-pg1-x530.google.com (mail-pg1-x530.google.com [IPv6:2607:f8b0:4864:20::530]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 293A1C0613DD for ; Tue, 13 Jul 2021 11:00:10 -0700 (PDT) Received: by mail-pg1-x530.google.com with SMTP id t9so22297846pgn.4 for ; Tue, 13 Jul 2021 11:00:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=aUnwvzo3iJx64EYOs36puVhqp9GJq4422krM2Lg28ME=; b=pjVheK0zx5si1i4Eb9s5pegJG0OMW2zAHJpyCgDLb3LtX1Y7fa51g9Hemt6Z6DEA5B /v76+1atkf1zQ5aFPBUpsRPz4HjJE18d79Q9YlRKj+0UqcQZGM03XgHRrRVstC4n+XGK peZGo/WocfT+2+8SfvpxTmo0BK7901uovyMvl6KIoctAtLEwmSpwggDxYZB/t5AVbTl+ E3DdQVUj6GjNNZv/AQv/mAKC9HxWGhq05FTWUtldVgs0FJcRm6GnPuC3x74hJINiQ1PY 3mKUU2TNNxzBC3hfT8L+AZiQNftgYjcHD2fpY/H9+04lDIbk7rS3HLa8DSoPWZFDOEjv Nzaw== 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=aUnwvzo3iJx64EYOs36puVhqp9GJq4422krM2Lg28ME=; b=oRlvCB5et1xm6cALZHyTfTcuKiG5w+aKodwyaTKY1ntIBgyMIEcTrCl/g7UEvpFFkB IfXZ3sUQeki9LlSUFXEeq8ek346FxEmGPf/HtbJ5N5GqOWnfJyVsMvO18UyXe3UJZqVb qf0+mFctJEUVpvePWnI8YEYiEDdOHcfuIiZ76t/ddSrS7hIB3t2qM3vGEkskzbCALo0S KSBsjXfwXKvNhaGPgHSG46Flc/sI/UvAq9tRId1QSp2rxoWXzHt0GpEAUomv6KZ9e3j4 EEybrE92VLMoH9eHVP3FGZfQ7onF4U6zFqp1lX2NuF6FiOx0wuPU0Vf6LFyI7zGSmGoz q1Eg== X-Gm-Message-State: AOAM531JnL1nm9CvZEKdzhld7ZKrHou9lF+YCnvgj9cb117rVT+/c2K0 8JBfl7lET8m9sxs0d9EGWe0WhA== X-Received: by 2002:a62:3045:0:b029:32b:880f:c03a with SMTP id w66-20020a6230450000b029032b880fc03amr5884323pfw.22.1626199209362; Tue, 13 Jul 2021 11:00:09 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id 133sm21494711pfx.39.2021.07.13.11.00.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 13 Jul 2021 11:00:08 -0700 (PDT) Date: Tue, 13 Jul 2021 18:00:05 +0000 From: Sean Christopherson To: isaku.yamahata@intel.com Cc: Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H . Peter Anvin" , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , erdemaktas@google.com, Connor Kuehl , x86@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, isaku.yamahata@gmail.com Subject: Re: [RFC PATCH v2 03/69] KVM: X86: move out the definition vmcs_hdr/vmcs from kvm to x86 Message-ID: References: <62b61eb968f867518aedd98a0753b7fd29958efb.1625186503.git.isaku.yamahata@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <62b61eb968f867518aedd98a0753b7fd29958efb.1625186503.git.isaku.yamahata@intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jul 02, 2021, isaku.yamahata@intel.com wrote: > From: Isaku Yamahata > > This is preparation for TDX support. > > Because SEAMCALL instruction requires VMX enabled, it needs to initialize > struct vmcs and load it before SEAMCALL instruction.[1] [2] Move out the > definition of vmcs into a common x86 header, arch/x86/include/asm/vmx.h, so > that seamloader code can share the same definition. ^^^^^^^^^^ SEAMLDR? I don't have a strong preference on what we call it, but we should be consistent in our usage. Same comments as the first two patches, without seeing the actual SEAMLDR code it's impossible review this patch. I certainly have no objection to splitting up this behemoth, but the series should be self contained (within reason).