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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id F29BEC433F5 for ; Tue, 23 Nov 2021 15:37:06 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 5A2116B006C; Tue, 23 Nov 2021 10:36:51 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 52AE16B0071; Tue, 23 Nov 2021 10:36:51 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 37D6C6B0072; Tue, 23 Nov 2021 10:36:51 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0187.hostedemail.com [216.40.44.187]) by kanga.kvack.org (Postfix) with ESMTP id 22FF66B006C for ; Tue, 23 Nov 2021 10:36:51 -0500 (EST) Received: from smtpin08.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id B509B894AC for ; Tue, 23 Nov 2021 15:36:40 +0000 (UTC) X-FDA: 78840597360.08.A3F4DB9 Received: from mail-pl1-f176.google.com (mail-pl1-f176.google.com [209.85.214.176]) by imf22.hostedemail.com (Postfix) with ESMTP id B1FA2191C for ; Tue, 23 Nov 2021 15:36:39 +0000 (UTC) Received: by mail-pl1-f176.google.com with SMTP id m24so17367382pls.10 for ; Tue, 23 Nov 2021 07:36:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=5VVg5sF/i5gU/ki52+bDwZvmQKpTX8HJeSrAf6kcWFQ=; b=U6HSgDxCZz53CGLYrJ7O5A0XNm09HecVxGKIpmb1gkV3apRWZ25N2jA23Ttyp2MYKZ K7PCL8IziOVl3IGVvcEKWxmZ7N5WFdDKaeFnFWDdTQL8q+kbkqylzTzEvEGM/qub8VsW 0kNCx9MqyC2snH1QR5CdErs3MA8OmHVtnhGLtP4QLDC7rwwGeLp30owwNo0TxBfgzp/4 z9A4yJ5wtwLQDky0itThd+HFGg3KslkVzZMf+De/ppvd/GGnqEzg8bvzIdr3jjCW1Wdw esOXbQYxDR8uPmd7RrzvIegmxMJgPyMy2od9otejx7jL7aU+uOEan4lmnuCo0jVl028f on6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=5VVg5sF/i5gU/ki52+bDwZvmQKpTX8HJeSrAf6kcWFQ=; b=CqofApzEFMjI2xfNEF7pTa23pU5vDNiNnRAlOacrLSZK5xSb5ELxgjoaXR+15Y6dUx +GsMQAkW3a3MbhXo+ttzLbHcuG9HmE2lus9fTNT7sSRu9BqlotqsBWVjcBWEsvgihEBF i5Akaz1tuw5AvWRwB9HzBCDRVZg+38CtVFOzJ6O9ubglEDeIETGBrLQ8KIGcuCQExk/L oqwDg3AG1u/huj4G6IgVXlnpojuOsIucUP4SSnKXVgc1Gw3DRPFZQz2wXTl8K8mS3gmc hiioPthE7SHsVGjU1MCNe3FT6GtrDXeUMFysppgbMWi3oxWlX6oPvOjmilABPlgKeZTW YjXw== X-Gm-Message-State: AOAM5313l4zylFAN6i69RuXHw93U3gXrnocxpBOKzsnAy3VTW1Rx+Pnh NspMZ8k202G/BiJPuoXFB1MggQ== X-Google-Smtp-Source: ABdhPJzN3VZxkHeunJB6N/YPoYEM/c03A9bU/hzxt4O7jM4g9pvIKKtkf8VdyZ1rwnxZzh/blb4dBw== X-Received: by 2002:a17:902:c78a:b0:142:1b7a:930 with SMTP id w10-20020a170902c78a00b001421b7a0930mr7959825pla.8.1637681799124; Tue, 23 Nov 2021 07:36:39 -0800 (PST) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id k14sm9384097pga.65.2021.11.23.07.36.38 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 23 Nov 2021 07:36:38 -0800 (PST) Date: Tue, 23 Nov 2021 15:36:35 +0000 From: Sean Christopherson To: Borislav Petkov Cc: Dave Hansen , Brijesh Singh , Peter Gonda , x86@kernel.org, linux-kernel@vger.kernel.org, kvm@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 Zijlstra , Srinivas Pandruvada , David Rientjes , Dov Murik , Tobin Feldman-Fitzthum , Michael Roth , Vlastimil Babka , "Kirill A . Shutemov" , Andi Kleen , tony.luck@intel.com, marcorr@google.com, sathyanarayanan.kuppuswamy@linux.intel.com Subject: Re: [PATCH Part2 v5 00/45] Add AMD Secure Nested Paging (SEV-SNP) Hypervisor Support Message-ID: References: <20210820155918.7518-1-brijesh.singh@amd.com> <5f3b3aab-9ec2-c489-eefd-9136874762ee@intel.com> <38282b0c-7eb5-6a91-df19-2f4cfa8549ce@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: B1FA2191C X-Stat-Signature: 4pg9i5spdwp5myyrcwuri6h8cbmpkr8d Authentication-Results: imf22.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=U6HSgDxC; spf=pass (imf22.hostedemail.com: domain of seanjc@google.com designates 209.85.214.176 as permitted sender) smtp.mailfrom=seanjc@google.com; dmarc=pass (policy=reject) header.from=google.com X-HE-Tag: 1637681799-789865 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Tue, Nov 23, 2021, Borislav Petkov wrote: > On Mon, Nov 22, 2021 at 02:51:35PM -0800, Dave Hansen wrote: > > By "supporting", do you mean doing something functional? I don't really > > care if ptrace() to guest private memory returns -EINVAL or whatever. > > The most important thing is not crashing the host. > > > > Also, as Sean mentioned, this isn't really about ptrace() itself. It's > > really about ensuring that no kernel or devices accesses to guest > > private memory can induce bad behavior. > > I keep repeating this suggestion of mine that we should treat > guest-private pages as hw-poisoned pages which have experienced a > uncorrectable error in the past. > > mm already knows how to stay away from those. Kirill posted a few RFCs that did exactly that. It's definitely a viable approach, but it's a bit of a dead end, e.g. doesn't help solve page migration, is limited to struct page, doesn't capture which KVM guest owns the memory, etc... https://lore.kernel.org/kvm/20210416154106.23721-1-kirill.shutemov@linux.intel.com/