From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pl0-f70.google.com (mail-pl0-f70.google.com [209.85.160.70]) by kanga.kvack.org (Postfix) with ESMTP id 02F446B0007 for ; Fri, 13 Jul 2018 00:18:16 -0400 (EDT) Received: by mail-pl0-f70.google.com with SMTP id e1-v6so18576758pld.23 for ; Thu, 12 Jul 2018 21:18:15 -0700 (PDT) Received: from mga14.intel.com (mga14.intel.com. [192.55.52.115]) by mx.google.com with ESMTPS id a24-v6si2338677pgh.357.2018.07.12.21.18.14 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 12 Jul 2018 21:18:15 -0700 (PDT) Subject: Re: [RFC PATCH v2 18/27] x86/cet/shstk: Introduce WRUSS instruction From: Dave Hansen References: <20180710222639.8241-1-yu-cheng.yu@intel.com> <20180710222639.8241-19-yu-cheng.yu@intel.com> <1531436398.2965.18.camel@intel.com> <46784af0-6fbb-522d-6acb-c6248e5e0e0d@linux.intel.com> <167645aa-f1c7-bd6a-c7e0-2da317cbbaba@intel.com> <55A0592D-0E8D-4BC5-BA4B-E82E92EEA36A@amacapital.net> <66016722-9872-a3f9-f88b-37397f9b6979@intel.com> Message-ID: <8bd46e0e-5418-0b22-d471-092d31c78320@intel.com> Date: Thu, 12 Jul 2018 21:18:01 -0700 MIME-Version: 1.0 In-Reply-To: <66016722-9872-a3f9-f88b-37397f9b6979@intel.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: owner-linux-mm@kvack.org List-ID: To: Andy Lutomirski Cc: Yu-cheng Yu , x86@kernel.org, "H. Peter Anvin" , Thomas Gleixner , Ingo Molnar , linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org, linux-mm@kvack.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, Arnd Bergmann , Balbir Singh , Cyrill Gorcunov , Florian Weimer , "H.J. Lu" , Jann Horn , Jonathan Corbet , Kees Cook , Mike Kravetz , Nadav Amit , Oleg Nesterov , Pavel Machek , Peter Zijlstra , "Ravi V. Shankar" , Vedvyas Shanbhogue On 07/12/2018 09:16 PM, Dave Hansen wrote: > On 07/12/2018 07:21 PM, Andy Lutomirski wrote: >> I am tempted to suggest that the whole series not be merged until >> there are actual docs. Ita??s not a fantastic precedent. > > Do you mean Documentation or manpages, or are you talking about hardware > documentation? > https://software.intel.com/sites/default/files/managed/4d/2a/control-flow-enforcement-technology-preview.pdf Hit send too soon... We do need manpages a well. If I had to do it for protection keys, everyone else has to suffer too. :) Yu-cheng, I really do think selftests are a necessity before this gets merged.