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 X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 70DB9C04FF3 for ; Fri, 21 May 2021 21:43:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 4CFDC613EE for ; Fri, 21 May 2021 21:43:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229540AbhEUVpG (ORCPT ); Fri, 21 May 2021 17:45:06 -0400 Received: from Galois.linutronix.de ([193.142.43.55]:56534 "EHLO galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229472AbhEUVpD (ORCPT ); Fri, 21 May 2021 17:45:03 -0400 From: Thomas Gleixner DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020; t=1621633418; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O2Zvf4YEm1tFPNzEd7n/UJedCF9RvfBvtdYegG4LEec=; b=iFF+GrJjH231ECxDi6mr1GS+vUU+Muc9cB7hxoXY+5Mqlmhu4PAbAfPaP6XJGNI0MJEoWV fbRXPRxJOM4XVuZOYkUSeTz4LoowD74WdZvUhbE+y21la0hu9hZq2ylnJVlqQ0CpTV4LHF YVXlhEaSgpUyrlTsNRAEj/BORwjunbOhu4sujqy0zrTjRPWOAzGqnPfXV3I/QXoq9AzN2B gHhTr0kX6LHLDByw5JYf3nRv2RskZ49+e45sAoMjkNi0D4KCMMNIAB2JDqsybpGePxKh6c qB4efT0uKcagFsa7Zw5loWSuTNeyp3GRNfpHiEOSqTeZBznxQ0huT+30yPy0Ng== DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/relaxed; d=linutronix.de; s=2020e; t=1621633418; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=O2Zvf4YEm1tFPNzEd7n/UJedCF9RvfBvtdYegG4LEec=; b=FQvivXj6EAnAS/ROEOttaW8WjCkuzfYbXboYPCGOpz+27FOorQZFKcw+ao6rwvRtr4Kie6 oUJHCIhRsRIj8iDA== To: Andy Lutomirski , Florian Weimer , Dave Hansen Cc: Dave Hansen via Libc-alpha , Len Brown , Rich Felker , Linux API , "Bae\, Chang Seok" , the arch/x86 maintainers , Linux Kernel Mailing List , Kyle Huey , Borislav Petkov , Keno Fischer , Arjan van de Ven , Willy Tarreau Subject: Re: Candidate Linux ABI for Intel AMX and hypothetical new related features In-Reply-To: <6c9c4597-a1af-4cbb-9dc8-424999d04793@www.fastmail.com> References: <20210415044258.GA6318@zn.tnic> <20210419141454.GE9093@zn.tnic> <20210419191539.GH9093@zn.tnic> <20210419215809.GJ9093@zn.tnic> <874kf11yoz.ffs@nanos.tec.linutronix.de> <87k0ntazyn.ffs@nanos.tec.linutronix.de> <37833625-3e6b-5d93-cc4d-26164d06a0c6@intel.com> <9c8138eb-3956-e897-ed4e-426bf6663c11@intel.com> <87pmxk87th.fsf@oldenburg.str.redhat.com> <939ec057-3851-d8fb-7b45-993fa07c4cb5@intel.com> <87r1i06ow2.fsf@oldenburg.str.redhat.com> <263a58a9-26d5-4e55-b3e1-3718baf1b81d@www.fastmail.com> <87k0nraonu.ffs@nanos.tec.linutronix.de> <6c9c4597-a1af-4cbb-9dc8-424999d04793@www.fastmail.com> Date: Fri, 21 May 2021 23:43:38 +0200 Message-ID: <87h7ivahkl.ffs@nanos.tec.linutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 21 2021 at 13:07, Andy Lutomirski wrote: > On Fri, May 21, 2021, at 12:10 PM, Thomas Gleixner wrote: >> Why? The bit can be enabled and #NM catches the violation of the ABI >> contract if the application did not request usage. No XCR0 fiddling on >> context switch required. > > XFD does nothing about signals. It's a matter of what's implemented in #NM. XFD just arms #NM > It also doesn=E2=80=99t help give applications a non-Linux-specific way t= o ask > if AMX is available. The SDM says that one can read XCR0. Sure, we > can use it, but cross platform libraries seem likely to get it wrong. Well, that's the inevitable consequence of Intel declaring that everything needs to be exposed unconditionally for the very wrong reasons. Thanks, tglx