Received: by 2002:a25:c593:0:0:0:0:0 with SMTP id v141csp415464ybe; Wed, 4 Sep 2019 01:35:52 -0700 (PDT) X-Google-Smtp-Source: APXvYqz9NFwxDVjp9n1dE5xoJh5s/BdG2cHbAt0WivWGzPUx5fzmia03kTDvmtC4WGGjVhNO/bKt X-Received: by 2002:a17:902:b202:: with SMTP id t2mr40436622plr.303.1567586152180; Wed, 04 Sep 2019 01:35:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567586152; cv=none; d=google.com; s=arc-20160816; b=ZysgJu5DuIxr6206udeXmu0DZdK5cdZq/Y9SYL7b/CeRsrRSsN1KlWLc3yVrIbxfSf 9S6VL2vNGEQo4qIXNxcfT5NXyr8XEFFU7K6uUcakSwa1H9tMfrnfCgRKiLnK+oi5g9wU xIEHZZ+kB8BdlowW1bHjp38HMxxJClvUtjU+5IBRvWOKFmPewNrFULSrVyZhXIAxSeiZ kbtJslyaxcgvO6xrIACk0q6Jvab7VLFRwHBta7cCrhTgeyqMeHDwF0I/b06E3KLNnMOq tC0xDUHDiX/ZGsfddyrxubKiub4QoTTQUn8fJsu/RiCrbgW0OgQogGFKFqX/RJFr5ahb i/EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:organization:from:references:cc:to:subject :dkim-signature; bh=zCDtcNpMSUrFny26vSCVojw71S8FYBHGEGqtjQbqNDA=; b=WXqbVHyhbFHwPCWyifYkQ4kyXLiz9+Ecixs0KixOUyexQ1ajBtdvg5YP/qgX2rrau2 KyxQSVQb+5VlcVVP7zwyUcnxtyigahNmwrMi4zQKOuEdITL28GiQ5AgrqBdZsbdIyhGU ymrJ2ynbrLLbnILdcb/VKeMI31776w8ELBR1JGsrBG8QycE0RpMv2RqQa1dVkkMHsd7m /+xPOvZOO8KBWhl/MDrVITzdzVCNu70tbaoB/9S2RTomTt2O2u8QHzsBKF9tvXPdOU26 pxhhxwB+1ys9eKD5l8bFYjRTWpRKTt/4QZBBEWPJcLVEvb/lOFQfHIE/tpA+uW9ojiYz 6AQA== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=J1VY4NLk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b62si16837773pgc.148.2019.09.04.01.35.36; Wed, 04 Sep 2019 01:35:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail (test mode) header.i=@shipmail.org header.s=mail header.b=J1VY4NLk; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727144AbfIDIeq (ORCPT + 99 others); Wed, 4 Sep 2019 04:34:46 -0400 Received: from ste-pvt-msa2.bahnhof.se ([213.80.101.71]:33339 "EHLO ste-pvt-msa2.bahnhof.se" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725774AbfIDIep (ORCPT ); Wed, 4 Sep 2019 04:34:45 -0400 Received: from localhost (localhost [127.0.0.1]) by ste-pvt-msa2.bahnhof.se (Postfix) with ESMTP id 51B553F5F0; Wed, 4 Sep 2019 10:34:28 +0200 (CEST) Authentication-Results: ste-pvt-msa2.bahnhof.se; dkim=pass (1024-bit key; unprotected) header.d=shipmail.org header.i=@shipmail.org header.b=J1VY4NLk; dkim-atps=neutral X-Virus-Scanned: Debian amavisd-new at bahnhof.se X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=6.31 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ste-ftg-msa2.bahnhof.se (amavisd-new); dkim=pass (1024-bit key) header.d=shipmail.org Received: from ste-pvt-msa2.bahnhof.se ([127.0.0.1]) by localhost (ste-ftg-msa2.bahnhof.se [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TF6Qxe2YrX2F; Wed, 4 Sep 2019 10:34:27 +0200 (CEST) Received: from mail1.shipmail.org (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) (Authenticated sender: mb878879) by ste-pvt-msa2.bahnhof.se (Postfix) with ESMTPA id 109A53F346; Wed, 4 Sep 2019 10:34:25 +0200 (CEST) Received: from localhost.localdomain (h-205-35.A357.priv.bahnhof.se [155.4.205.35]) by mail1.shipmail.org (Postfix) with ESMTPSA id 25C2136117F; Wed, 4 Sep 2019 10:34:25 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=shipmail.org; s=mail; t=1567586065; bh=MbtBfVZaBumDkBlAtpFFrFhKmgiWkoQ1b1+zCTqFcPk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=J1VY4NLk8W4zmUOI/PrVpikNX2CTceCnda/zQbfYcicCF3vdBOuNsDCJA92eFp5ht 3lD12c2pd8Zfdi7N5HHMYy89RLMKOp4gwBPCXMmdA/a6GjY6jA2yivh93n/ObwJ+L3 Bnjg6fVWttF9EPPWca+yjsxjPyKFv0Igx7Tf3A8c= Subject: Re: [PATCH v2 3/4] drm/ttm, drm/vmwgfx: Correctly support support AMD memory encryption To: Dave Hansen , Andy Lutomirski Cc: Daniel Vetter , dri-devel , pv-drivers@vmware.com, VMware Graphics , Linux Kernel Mailing List , Tom Lendacky , Thomas Hellstrom , Peter Zijlstra , Dave Hansen , Heiko Carstens , Christian Borntraeger , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Thomas Gleixner , =?UTF-8?Q?Christian_K=c3=b6nig?= References: <20190903131504.18935-1-thomas_os@shipmail.org> <20190903131504.18935-4-thomas_os@shipmail.org> <6d0fafcc-b596-481b-7b22-1f26f0c02c5c@intel.com> <7fa3b178-b9b4-2df9-1eee-54e24d48342e@intel.com> <44b094c8-63fe-d9e5-1bf4-7da0788caccf@shipmail.org> <6d122d62-9c96-4c29-8d06-02f7134e5e2a@shipmail.org> <2759de53-123f-5972-a246-bbf959439c5d@intel.com> From: =?UTF-8?Q?Thomas_Hellstr=c3=b6m_=28VMware=29?= Organization: VMware Inc. Message-ID: Date: Wed, 4 Sep 2019 10:34:24 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <2759de53-123f-5972-a246-bbf959439c5d@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Dave, On 9/4/19 1:10 AM, Dave Hansen wrote: > Thomas, this series has garnered a nak and a whole pile of thoroughly > confused reviewers. > > Could you take another stab at this along with a more ample changelog > explaining the context of the problem? I suspect that's a better place > to start than having us all piece together the disparate parts of the > thread. Sure. I was just trying to follow up on the emailsĀ  to get a better understanding what got people confused in the first place. Thanks, Thomas