From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) by sourceware.org (Postfix) with ESMTPS id B70C53857C7E for ; Fri, 26 Mar 2021 20:44:27 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org B70C53857C7E Received: by mail-ot1-x332.google.com with SMTP id m21-20020a9d7ad50000b02901b83efc84a0so6402560otn.10 for ; Fri, 26 Mar 2021 13:44:27 -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=IaZsiof8k2Nsj0E+BzNEoPoEx7nmUs5gquVCswdhQ/Y=; b=Krp5tDcqdJWNrEF65V0t43cg+v+z7TNRiXytuz1rJ47N0rDg57i/FKcd8OoWttVKQX nP11ZFGBSVtwQA3Nytmh6P1P/cUQ4Pz/Wic8Gw3AdxFSJJvG3/ylBLRTCfjanjElbq9h hHAej4yvfY6sJvx3n01jQIqbZu4xnh8b7ASgwXAZMs1Nnm/jUlGeAaaVP8al5aXvlAzI ZKoLKfTZWgiX8taSmKi6gUoAHgA4/KsEhidFcIAVuTdgU4+FTWWYysQaf8VApseoCcIq KvYvUCxeTrreRAXwV41GadaqnKCIuGgDXpiyE/hZuC8PY6n7GwvLPm5/7oC94AYjxdtZ hZlA== X-Gm-Message-State: AOAM530N9EXZNsQrghmnSP8yS1znSOkzEx3nvG8ICOJHXmhotXszCebK ritEuwkEknHXWaIP68lTVhqsqzz/F0aDA8R9r9c= X-Google-Smtp-Source: ABdhPJxO1p8gA3bgvG7L/wp9utF+Mnhs32CNzBHXk80UJs+BAuGYx87M7HYJOLl69n5/quEFQcW9jKBTg99B8eYx4go= X-Received: by 2002:a05:6830:90c:: with SMTP id v12mr13024801ott.179.1616791467155; Fri, 26 Mar 2021 13:44:27 -0700 (PDT) MIME-Version: 1.0 References: <87a6qqi064.fsf@mid.deneb.enyo.de> <87blb5d7zx.fsf@mid.deneb.enyo.de> <877dltd569.fsf@mid.deneb.enyo.de> In-Reply-To: <877dltd569.fsf@mid.deneb.enyo.de> From: "H.J. Lu" Date: Fri, 26 Mar 2021 13:43:51 -0700 Message-ID: Subject: Re: Why does glibc use AVX-512? To: Florian Weimer Cc: Andy Lutomirski , X86 ML , LKML , "Bae, Chang Seok" , "Carlos O'Donell" , Rich Felker , libc-alpha Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3030.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, 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, 26 Mar 2021 20:44:28 -0000 On Fri, Mar 26, 2021 at 1:35 PM Florian Weimer wrote: > > All this needs to work transparently without user intervention. We > cannot require firmware upgrades to fix the incorrect RTM reporting > issue (the bug I referenced). I think we can require software updates > which tell glibc when to use RTM-enabled string functions if the > dynamic selection does not work (either for performance reasons, or > because of the RTM reporting bug). > > I want to avoid a situation where one in eight processes fail to work > correctly because the CPUID checks ran on CPU 0, where RTM is reported > as available, and then we trap when executing XTEST on other CPUs. glibc can disable RTM based on CPU model and stepping. -- H.J.