Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp4535666pxf; Tue, 30 Mar 2021 10:04:36 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyY6siLXkqtJaqx4HQf8CYSo6UkDhi+c3OR9l5/vakJ4NA1yJLqoPN3CHf7bXJRHtswGs3x X-Received: by 2002:a17:906:ad85:: with SMTP id la5mr34066772ejb.37.1617123876276; Tue, 30 Mar 2021 10:04:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617123876; cv=none; d=google.com; s=arc-20160816; b=yl1Pr4Xqef3AZVFZpnNZCH7xQSKD6UV/f5CFIBeWHVcUGEwE+J0oVw2ofNVbE2YXiJ pOyYNRaUm94jpBXkdp4JheUYI0yWvuFSIv2pZYpgcbwHeZ5Cz/LksNAKa7uqq6P3iFou 1oAXNRv6vprtSpWEkYvhuOGamGDGLVpYH/XVMSoooLYnjUK8EhClQuaYVQdWa75rmYWg YkNsBiGcY1SAftrUyDZw7FWfqsJE6PdEL//qbDLdJzrqCqRtvw+2hv/qm9AKXNlXg6uV kteZ30pFfQcO/AxAAjRrmBWMcVdn9LwxRq6knF0yn+Nd5BxZ0xMp6AD2P0xnThX3SrIE 4pKg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=ACAk4CMQCpfK7ShWMIgNHXJw2kj1X4hF0oXL0+B1bYU=; b=oS2nmsIbB2eub7NodMhXsf50uUP90ibgfEMXFpAF+vYIsn03f9Rczy5T+m95fwhYFb TuQAVD0ep3ZDQcrbElPqQHyOG7u2PJ0zIBPTXTVDluWWTn8sLl+I4AD+B/QAQdo2yYud V78+DBfLgYFPGXheqiwNcGE6ULtPvhHSviOHumV+/1OKcNiC1LOovnTLjxPFv6OMofHx WsYVcDFATTn4rK2yqv+l359mOvc23HM+35ryOCNuD3FJGz9GH0FVnRp7TsBvhif7soM/ PDKyOETvAnOpx8v12rodD2u9B/KrT1/+LvUrjTwfa2QX2m/Q3Z+wD4ruP6UodG1KJLWm dPiw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id d12si15575362edx.162.2021.03.30.10.04.13; Tue, 30 Mar 2021 10:04:36 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232459AbhC3RCa (ORCPT + 99 others); Tue, 30 Mar 2021 13:02:30 -0400 Received: from mail-ej1-f48.google.com ([209.85.218.48]:40680 "EHLO mail-ej1-f48.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232784AbhC3RBT (ORCPT ); Tue, 30 Mar 2021 13:01:19 -0400 Received: by mail-ej1-f48.google.com with SMTP id u9so25874402ejj.7; Tue, 30 Mar 2021 10:01:18 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ACAk4CMQCpfK7ShWMIgNHXJw2kj1X4hF0oXL0+B1bYU=; b=GdleGBszUcIxMc8Fp1BZGjq2pMexJr5m3KcCTf4vqvZRFSBQibZmt9mfRi52kcVMvg Vif8/oWxlsGqN96Gh4+1xDw66NozAmO9lrDDsVXs9Q9ZTA4oWy2LcaVOy2CIBeN+CWIX CM6mRmli3imKMq7j2FhlM2z+RAUDWkOvRnCp3IDLhb5nE6jiSV6QagurUzm2L6INEjEf CrfwBZRb6yo1Ilu08oiVNCY4tcG+Sbdv2Hi5gNBQkRx/vuXRJ0nBDw5XaFmK8efOVrBo 5Ivv4Y8nOEJD78qAuawBDb67ejam1dGG+2C6+x1tR1f7GUj6nRkB2lg996YaSv8fCCJ5 oW2g== X-Gm-Message-State: AOAM531J5uhxnNxapacZmXlhZxoxN/9+a0s/8lExeifR4dSZcI3ynHjh 1OliB+JfI7VrOccgzk552fDkrSeqqzckMTmZGB0= X-Received: by 2002:a17:906:340f:: with SMTP id c15mr21662769ejb.317.1617123677867; Tue, 30 Mar 2021 10:01:17 -0700 (PDT) MIME-Version: 1.0 References: <5F98327E-8EC4-455E-B9E1-74D2F13578C5@amacapital.net> In-Reply-To: From: Len Brown Date: Tue, 30 Mar 2021 13:01:06 -0400 Message-ID: Subject: Re: Candidate Linux ABI for Intel AMX and hypothetical new related features To: Andy Lutomirski Cc: Greg KH , "Bae, Chang Seok" , Dave Hansen , X86 ML , LKML , libc-alpha , Florian Weimer , Rich Felker , Kyle Huey , Keno Fischer , Linux API Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Andy, I agree, completely, with your description of the challenge, thank you for focusing the discussion on that problem statement. Question: Is it required (by the "ABI") that a user program has everything on the stack for user-space XSAVE/XRESTOR to get back to the state of the program just before receiving the signal? My understanding is that there are programs that do this. However, if it is not guaranteed to work, that could greatly simplify what we are required to put on the signal stack. thanks, -Len