From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from galois.linutronix.de (Galois.linutronix.de [193.142.43.55]) by sourceware.org (Postfix) with ESMTPS id E1A8A385E440 for ; Fri, 21 May 2021 21:43:39 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org E1A8A385E440 From: Thomas Gleixner 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 X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 21 May 2021 21:43:41 -0000 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