Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp1612734pxv; Fri, 16 Jul 2021 13:23:43 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwF4NOCXhjB/AlB/hd5VOjIWuAZVimVYcC4vMKk6nsqvJMcba9qeA3xF9T3DJyhxQYWMreC X-Received: by 2002:a6b:4f16:: with SMTP id d22mr8731112iob.15.1626467023418; Fri, 16 Jul 2021 13:23:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626467023; cv=none; d=google.com; s=arc-20160816; b=E+WNsOH666jUyNxDkeJWfSGZxezJmDqLJ21Ze3obTGMy3wyssLQrawb7xkyM4N42d6 2/GmNvvHqk52vPVzeg2GBWUcwEt0NJDpKfsV+4s/AZMS+QU50y+JeVg93x+Z39WHHNhs EyKaKHMwFTs5F1Qd0+q3EPY3hCzA54OgrrMce8J0wtzQURFhukg4l59gYT2By/I/nN1a vNEVPTAWThzJH3YJ3eTebmZkwszIvKi+oSE4hbHrLBC6OLej1jA3GrqmvKEfspfgUfnX 04uO4c/40yqSPKnSJdePI+Ni00hdT+0uK8QqhG1sbl5l0FeGcRyEQxd3omF4OmFwnuFa EcFQ== 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=x85rFiYKbp37maDQJOeVsTrROe6NzpgrCb0rCmLZT5M=; b=Vh33wwj/WeZW56mj6mhwjxOlpeSP0vFgbcw/6FCmfPB30d1Qtv1yuNrTbB4kMVUz1O L2DQ/ZpI7iVTwLc1dQwS8hfFdKeJ0K7otXFbDPHqnAPH46Fl9LmxuPT1AQkKGmymV2fW Uk8Te/pmV8m4pW0XVz7zjsUHbc3nYxhjeV9qoTl6YJJ2pVAUGAu9+qLwxtFIgclFt0Jb Sjfjow5El4c9oYsmcmUTNvLIfnKWxlh6vAvZ4L4vwibVx3GwEZHBniBu70a+dXV4Z+be M0+yYlpb1ItVbxmMylNT2BfzENKxHL9PnXlS5yQQvYBx7MYnkGyzttYV6TKy+OP7REom viow== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20161025 header.b=A3iaz5af; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-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 b15si9847737ilj.38.2021.07.16.13.23.30; Fri, 16 Jul 2021 13:23:43 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-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=A3iaz5af; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-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 S230172AbhGPU0B (ORCPT + 99 others); Fri, 16 Jul 2021 16:26:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38164 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232524AbhGPU0A (ORCPT ); Fri, 16 Jul 2021 16:26:00 -0400 Received: from mail-pg1-x536.google.com (mail-pg1-x536.google.com [IPv6:2607:f8b0:4864:20::536]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6D72CC061765 for ; Fri, 16 Jul 2021 13:23:04 -0700 (PDT) Received: by mail-pg1-x536.google.com with SMTP id w15so11028119pgk.13 for ; Fri, 16 Jul 2021 13:23:04 -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=x85rFiYKbp37maDQJOeVsTrROe6NzpgrCb0rCmLZT5M=; b=A3iaz5afAQGHEMb5dAx2xN1+E/Jkl1exglVeIMNRgB04QPj2THSJNWjFHH4urOC4dj azzuyrfh/0lup7t52U45wwGHGx8zncavC+7HwrEL3oJwy/PeRI46jUEK0qujvYADefKM ArovxtIPS/UAgoxpNVVFKG1HXyvqmh/SOMk3r2oZmO0lj0BNXSOSYxiq86oLWGpzEqzx KFUbSDnqnzAODG1aEbYMh+kDC3D+M6SXrMy0/MM0ejw2dka6jMwj5/ZiAjC+QAPQ0dBB tZ2XeFnfbp2L4X1kFk+q9un5p8BAkl8dwzio2EB2PCFjXW8QMJqBrsIbUOddU2P4I+C3 O5Pg== 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=x85rFiYKbp37maDQJOeVsTrROe6NzpgrCb0rCmLZT5M=; b=YKKiSnWSrSnwLcziyuGRm0kZhSb/wyJHqLZhl81DZzzZKPYV2VXBYZlVisD+sQp7+E jMrW0yqXX0rifb2WmhqB5cqG9QdMxC6+sMkKA7qPZpEcH16v+gWtJpBLE6ICLWONxfbq q5IhJ5jvG9FsgyAADINWW0I41wQFflPYj0d+x5vReQmoUKONkD4VUx65fTCbglynjV47 YKirf6QRSuLCvCiPCPbdxm/zuvKTo4G1Va83xmVRj3NYTrvDmTo5EIQMVZsTDSEBf7bC kTodLpQRTwYh4t0Hm99Ebd0hHUlZYvkUO7pzH18EUad+OYpntcD5eQY20YT38hAFNOX9 7SEg== X-Gm-Message-State: AOAM531rLgFYsq6J1dt1UwGJZ6N7NAABwfJGRjtdcQlkCZlwFj+Ukbpx YPnynpdGQEDj6vCypJDn2XkQpw== X-Received: by 2002:a63:1e59:: with SMTP id p25mr11432905pgm.110.1626466983659; Fri, 16 Jul 2021 13:23:03 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id o134sm11534516pfg.62.2021.07.16.13.23.02 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 16 Jul 2021 13:23:03 -0700 (PDT) Date: Fri, 16 Jul 2021 20:22:59 +0000 From: Sean Christopherson To: Brijesh Singh Cc: x86@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, linux-efi@vger.kernel.org, platform-driver-x86@vger.kernel.org, linux-coco@lists.linux.dev, linux-mm@kvack.org, linux-crypto@vger.kernel.org, Thomas Gleixner , Ingo Molnar , Joerg Roedel , Tom Lendacky , "H. Peter Anvin" , Ard Biesheuvel , Paolo Bonzini , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Andy Lutomirski , Dave Hansen , Sergio Lopez , Peter Gonda , Peter Zijlstra , Srinivas Pandruvada , David Rientjes , Dov Murik , Tobin Feldman-Fitzthum , Borislav Petkov , Michael Roth , Vlastimil Babka , tony.luck@intel.com, npmccallum@redhat.com, brijesh.ksingh@gmail.com Subject: Re: [PATCH Part2 RFC v4 30/40] KVM: X86: Define new RMP check related #NPF error bits Message-ID: References: <20210707183616.5620-1-brijesh.singh@amd.com> <20210707183616.5620-31-brijesh.singh@amd.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210707183616.5620-31-brijesh.singh@amd.com> Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Nit, please use "KVM: x86:" for the shortlogs. And ubernit, the "new" part is redundant and/or misleading, e.g. implies that more error code bits are being added to existing SNP/RMP checks. E.g. KVM: x86: Define RMP page fault error code bits for #NPT On Wed, Jul 07, 2021, Brijesh Singh wrote: > When SEV-SNP is enabled globally, the hardware places restrictions on all > memory accesses based on the RMP entry, whether the hyperviso or a VM, Another typo. > performs the accesses. When hardware encounters an RMP access violation > during a guest access, it will cause a #VMEXIT(NPF).