From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ed1-f53.google.com (mail-ed1-f53.google.com [209.85.208.53]) by sourceware.org (Postfix) with ESMTPS id 8D2663858024 for ; Sat, 17 Apr 2021 01:57:43 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 8D2663858024 Received: by mail-ed1-f53.google.com with SMTP id bx20so33223451edb.12 for ; Fri, 16 Apr 2021 18:57:43 -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=Jo74dkJt7xqUoXDWytSGjWDUiJiuB264VMFRwEGPHI4=; b=Og19W4f0eoD5jug6XAd0oYXnH/A//C1cyRJoWtPG3U4UQsF3iv5dUkl27+f9JUsuZK 27tnt3NZdzJbfE7PQKe+udLASLtO9T0HX7w0G+5co3gcq0G5QAkfZzZK5tR6p+LyKu5S NAs0AL5SovXQuF0eYbExoPbfZwzshJjw1SkilHT8kIkSKOM/AUTv5eVuc8adexoZmbUp h2XW5qfi9s5eRpZhakXas8LEjBSNeI9aYSlyFs6DNZLBfKZWHR4A+P6aHXbb9DuhLzs6 K0QTxBMa3qsH/rrJVMo/Gr+PXYtEqNxUJrn+hZOpFDGumyqRbeS4Z0ZOJsiYFyUEELno SuZQ== X-Gm-Message-State: AOAM531zF3Zlz6icaqMF2Mb7g6w9emISVhdQziIhd+ID3tMzc3J90R80 6CifiYkFzqxTXqEXunN9JGeOMVFGnC4O5zRWaaA= X-Google-Smtp-Source: ABdhPJyIqg5OuLyLoiKaIg7RcVsHIcICQfAyLflM9kU/vz762xy5bBys6eKAw2sljUMooVjAvTvCb3E92clKD/nOYwA= X-Received: by 2002:aa7:c144:: with SMTP id r4mr13488454edp.222.1618624662590; Fri, 16 Apr 2021 18:57:42 -0700 (PDT) MIME-Version: 1.0 References: <87lf9nk2ku.fsf@oldenburg.str.redhat.com> In-Reply-To: From: Len Brown Date: Fri, 16 Apr 2021 21:57:31 -0400 Message-ID: Subject: Re: Candidate Linux ABI for Intel AMX and hypothetical new related features To: Andy Lutomirski Cc: Willy Tarreau , Florian Weimer , "Bae, Chang Seok" , Dave Hansen , X86 ML , LKML , linux-abi@vger.kernel.org, "libc-alpha@sourceware.org" , Rich Felker , Kyle Huey , Keno Fischer Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00, FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FORGED_FROMDOMAIN, FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS, KAM_DMARC_STATUS, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no 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: Sat, 17 Apr 2021 01:57:54 -0000 On Fri, Apr 16, 2021 at 6:14 PM Andy Lutomirski wrote: > My point is that every ... I encourage you to continue to question everything and trust nobody. While it may cost you a lot in counseling, it is certainly valuable, at least to me! :-) I do request, however, that feedback stay specific, stay technical, and stay on-topic. We all have plenty of real challenges we can be tackling with our limited time. > Is there any authoritative guidance at all on what actually happens, > performance-wise, when someone does AMX math? Obviously, I can't speak to the performance of AMX itself pre-production, and somebody who does that for a living will release stuff on or before release day. What I've told you about the performance side-effects on the system (and lack thereof) from running AMX code is an authoritative answer, and is as much as I can tell you today. If I failed to answer a question about AMX, my apologies, please re-ask it. And if we learn something new between now and release day that is relevant to this discussion, I will certainly request to share it. Our team (Intel Open Source Technology Center) advocated getting the existing public AMX documentation published as early as possible. However, if you are really nto the details of how AMX works, you may also be interested to know that the AMX hardware patent filings are fully public ;-) cheers, Len Brown, Intel Open Source Technology Center