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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, 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 950E0C54FD0 for ; Mon, 20 Apr 2020 19:29:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 6F36120782 for ; Mon, 20 Apr 2020 19:29:27 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=intel-com.20150623.gappssmtp.com header.i=@intel-com.20150623.gappssmtp.com header.b="Ew/qZu4s" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726836AbgDTT30 (ORCPT ); Mon, 20 Apr 2020 15:29:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40776 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726189AbgDTT3Z (ORCPT ); Mon, 20 Apr 2020 15:29:25 -0400 Received: from mail-ej1-x641.google.com (mail-ej1-x641.google.com [IPv6:2a00:1450:4864:20::641]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 63CE1C061A0F for ; Mon, 20 Apr 2020 12:29:25 -0700 (PDT) Received: by mail-ej1-x641.google.com with SMTP id n4so8904924ejs.11 for ; Mon, 20 Apr 2020 12:29:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=intel-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Ce20/CIQIX522RaPVTyPTfJEPqiyAriKhvUnxTulqdM=; b=Ew/qZu4sDhUqxZ/TYFqRH0ERtCxbKG4Z8viu2sPjWVDAgBWlvcnLRlRx5rwXTM/Oah mIYHqq0r+8iblP15rxoSx33CEyZunyDuuLZACk8dgur1ueNplknlYmcAylmjCtPf23DA W9fH6ydZ1sJNeXLG+uo/C5iF+Bx7zwA18kCdy3xNxw5iz8+YxTIHSDrMrmLspd9T1TpP ntKFG8X9R+1/qJUVjBuCLfLmn2FSJJekaPBY9XT3Vh9StB1/hFnewJwuLeKxA0WHVKuW mtpVxRXs6eZYVS5FIIcDdh1u3GSNKMaWuB1GMxDd8IXaXWIKV6KMRQ2rSrylkdDm8eYG MzqQ== 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=Ce20/CIQIX522RaPVTyPTfJEPqiyAriKhvUnxTulqdM=; b=njpUjEK7VR7oCVJ8dTjJKvOQdDLn9uZWf3fDVMcvo5vHAMQAC3b65wsEaRxFL33Wmn I3vyXHzZ6scMlB5tDIXTieN37KaCKCr75ajuDaHW00Eg7IzIfrKri7HkCE5K6onXsNRd u1+NA6v4zvHT52M5kFGg/sUgNE0vUMnk75Rr+PiORcc7ohU/KPBI9PX1ciLl1OqWlxbd ZAG2B2EWD395vVGqBma1ln0v88msG0CbAUCHIO8cotZ4zAr80S0VJJzMSoscO/xb51CO SmwWem4mZC82XuWh/HdXOV9Bpq8+ZxUy68Y9irqj6lLiW7vePTs9qf8ABOOdzXi7zC2w ia5Q== X-Gm-Message-State: AGi0PuYwyf6m/z2lDnevkwoisPaCryyTz690ReqEvVN0idOYH84NqUwI asUh54oRu1Q9XyJxBliQMNVuuhRRrA8goqEn0/y9/g== X-Google-Smtp-Source: APiQypK9aQrIzZ87xSipVCdNGdFMMM1E4PzK+Awa+HpCEy9iTdMb3+e2PhmQ2RqaH5oAUbvtfE2smMIkNiOOGSkMCww= X-Received: by 2002:a17:906:6d8e:: with SMTP id h14mr17131940ejt.123.1587410964104; Mon, 20 Apr 2020 12:29:24 -0700 (PDT) MIME-Version: 1.0 References: <67FF611B-D10E-4BAF-92EE-684C83C9107E@amacapital.net> In-Reply-To: From: Dan Williams Date: Mon, 20 Apr 2020 12:29:12 -0700 Message-ID: Subject: Re: [PATCH] x86/memcpy: Introduce memcpy_mcsafe_fast To: Linus Torvalds Cc: Andy Lutomirski , Thomas Gleixner , Ingo Molnar , X86 ML , stable , Borislav Petkov , "H. Peter Anvin" , Peter Zijlstra , Tony Luck , Erwin Tsaur , Linux Kernel Mailing List , linux-nvdimm Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Apr 20, 2020 at 12:13 PM Linus Torvalds wrote: > On Mon, Apr 20, 2020 at 11:20 AM Dan Williams wrote: [..] > I really really detest the whole mcsafe garbage. And I absolutely > *ABHOR* how nobody inside of Intel has apparently ever questioned the > brokenness at a really fundamental level. > > That "I throw my hands in the air and just give up" thing is a > disease. It's absolutely not "what else could we do". So I grew up in the early part of my career validating ARM CPUs where a data-abort was either precise or imprecise and the precise error could be handled like a page fault as you know which instruction faulted and how to restart the thread. So I didn't take x86 CPU designers' word for it, I honestly thought that "hmm the x86 machine check thingy looks like it's trying to implement precise vs imprecise data-aborts, and precise / synchronous is maybe a good thing because it's akin to a page fault". I didn't consider asynchronous to be better because that means there is a gap between when the data corruption is detected and when it might escape the system that some external agent could trust the result and start acting on before the asynchronous signal is delivered.