Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp912610imu; Fri, 7 Dec 2018 10:51:05 -0800 (PST) X-Google-Smtp-Source: AFSGD/VX0lEu8fW+kk+RYKyE9XbAdU4vnI5X1MkJec0tcOHHOhPMtGFRVJDo+3+wE/c6eFlegJYM X-Received: by 2002:a17:902:24e7:: with SMTP id l36mr3195675plg.61.1544208665058; Fri, 07 Dec 2018 10:51:05 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544208665; cv=none; d=google.com; s=arc-20160816; b=m5jRE4y23hddFlix9t7+34dmmFRHq0lV5u5hvYIUrnqj3ktLEjFGDs8SIunEvCDNG+ PjCVo9q4EQwq+s+aFtBx8P+rSAp0C/QYRRtdIFqT5Z1EPZ1FOllQjvfa5e6VxnCgUNFr pCmRJwd4QgrjkvJsZqDM72MGXY7ww+1kNw8ROWzRQGNMOgTwFjgGohOSGiBVWzfODyLG ZsQ38GotOMqGnfn2bj4TouJTPometZ/3X3WS2HJ56EXYlqxKAoCeEtMoBKEDq2uRelG9 vMZxPn0e4/3VDfanKyABTm/juR73ZsfJRwV0UPc9nAfF65rgJcIBYANSHIvHFaw2/cUX Qxqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:to:references:message-id :content-transfer-encoding:cc:date:in-reply-to:from:subject :mime-version:dkim-signature; bh=Nnht3jCBryS9HUgUX34dDS3skyULy3W1Q28HHDlxc9U=; b=dUvzGsrMbxhkb4HwMMqK3GUweahAoT6U40xuSUGpnd8LoouDsAwkaY2cvhziLJQWGx 5e3OsU8IvtMv71rodyW5K+7Z8dlPAfSsnSezZqE1NY5dJVb8Jm4EpWw/KSqaV42ccWeq HyKB64V4D2Pwvrg/DA+ixRm49WDBASw547lz2nbwu8LwjDszcUuXbDf/TD/xNyUpZj6z UxkO/L4mWP+ZPfKBrNVSbCclwuUY2Nsi1vMg13ExDPG/QndGvUhflTaY3q3prLxs5Vdh dFY2zLpzuVhrar64Wg9o96WqPecG9+3N56C4lHugka//z9mmBnyczXlSUR0hrH7irsle YE6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@amacapital-net.20150623.gappssmtp.com header.s=20150623 header.b=YwRORVwq; 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 q189si3791253pfb.62.2018.12.07.10.50.49; Fri, 07 Dec 2018 10:51:05 -0800 (PST) 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=pass header.i=@amacapital-net.20150623.gappssmtp.com header.s=20150623 header.b=YwRORVwq; 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 S1726079AbeLGSuN (ORCPT + 99 others); Fri, 7 Dec 2018 13:50:13 -0500 Received: from mail-pg1-f193.google.com ([209.85.215.193]:35506 "EHLO mail-pg1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726011AbeLGSuM (ORCPT ); Fri, 7 Dec 2018 13:50:12 -0500 Received: by mail-pg1-f193.google.com with SMTP id s198so2099350pgs.2 for ; Fri, 07 Dec 2018 10:50:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amacapital-net.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nnht3jCBryS9HUgUX34dDS3skyULy3W1Q28HHDlxc9U=; b=YwRORVwqg21IflGLnDmUsqeyjek2uDpYvvFaC0BXK7DnX3L5aAzZ32Q1ruynaSEVRb /9BKIVNGl59ZN/Sx8137RpijJM8uI9WX+OlUMW0KFTCmsjE7VcA0eLsSFcN0WAcweJ70 rCLYyfCa6Qo5uDrxRoMN1CtqaF3iEIHlErubjDIRYJRQQjgg+P4lNR9gAGlP7EWXNGFn Is7a/+6zDKV/dfeLzh6a2rxOHvXNaz1jdC8j/cob1/oRyJu0J9r/s/1y9iXaJtKl2wkL mjS8qjwL2N+9CtsDFJsnPzX8DB5AelpD76K08eIq+krW6FxkWiBumHsZpXlWR8m7FCgh 5uqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=Nnht3jCBryS9HUgUX34dDS3skyULy3W1Q28HHDlxc9U=; b=l9g8rgPe44bhp7wg7O0GvHiN5EdItCVnRVD4NAVXw9dQbOk+yXJ0VOfMb2L9cz3kye N2NlKyP1OoaLOnUYx9toB7lJ4xjUCsuDbG8d0pok9S/i1LEA/KTw8pV4ChjrMi6iacdm dovEWaKX1kPCcoYwYBnzOVJW5WopM2PXgTFv6T6Bhdx0XufNPLN7KpU4ooxCNSi5i6Qu w4hmUoeDbgJwKWt5bNCG7h/PzZxiBvS8yogzwMlwnR/sIKrF3GJL0qW9x0E6ocGOl5/E efdUJX1FiNDDM0+z7W/6JC/aLmgdOE03ts6wCn3Fp0CNgqIF8MpAjiUGOiKD2W8/Pc8E xh0w== X-Gm-Message-State: AA+aEWa5MIXuqlK3Zd0xgwSSqlTYQe7BLOZei0FO4Hj2hukJVPlB0eoX pSjAG0LWlngtw75fGcTcPSxlJqF0efM= X-Received: by 2002:a62:5182:: with SMTP id f124mr3377934pfb.238.1544208611377; Fri, 07 Dec 2018 10:50:11 -0800 (PST) Received: from ?IPv6:2600:1010:b02e:9276:b497:ca3d:93db:f61e? ([2600:1010:b02e:9276:b497:ca3d:93db:f61e]) by smtp.gmail.com with ESMTPSA id z127sm5835307pfb.80.2018.12.07.10.50.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 07 Dec 2018 10:50:10 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (1.0) Subject: Re: [RFC PATCH v2 4/4] x86/vdso: Add __vdso_sgx_enter_enclave() to wrap SGX enclave transitions From: Andy Lutomirski X-Mailer: iPhone Mail (16B92) In-Reply-To: <59c989a1-e699-9665-780f-6dd263f41ce4@intel.com> Date: Fri, 7 Dec 2018 10:50:08 -0800 Cc: Jethro Beekman , Sean Christopherson , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "x86@kernel.org" , Dave Hansen , Peter Zijlstra , "H. Peter Anvin" , "linux-kernel@vger.kernel.org" , Jarkko Sakkinen , Josh Triplett , Haitao Huang , "linux-sgx@vger.kernel.org" , "Dr. Greg" Content-Transfer-Encoding: quoted-printable Message-Id: <85EE19AF-C085-4E17-A673-44242996AF75@amacapital.net> References: <20181206221922.31012-1-sean.j.christopherson@intel.com> <20181206221922.31012-5-sean.j.christopherson@intel.com> <59c989a1-e699-9665-780f-6dd263f41ce4@intel.com> To: Dave Hansen Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > On Dec 7, 2018, at 10:44 AM, Dave Hansen wrote: >=20 >> On 12/7/18 10:15 AM, Jethro Beekman wrote: >> This is not sufficient to support the Fortanix SGX ABI calling >> convention, which was designed to be mostly compatible with the SysV >> 64-bit calling convention. The following registers need to be passed in >> to an enclave from userspace: RDI, RSI, RDX, R8, R9, R10. The following >> registers need to be passed out from an enclave to userspace: RDI, RSI, >> RDX, R8, R9. >=20 > Are you asking nicely to change the new Linux ABI to be consistent with > your existing ABI? Or, are you saying that the new ABI *must* be > compatible with this previous out-of-tree implementation? I think that allowing the enclave to return at least a few registers is quit= e reasonable, but I don=E2=80=99t have a strong opinion.=