Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp4213278imu; Fri, 30 Nov 2018 13:02:07 -0800 (PST) X-Google-Smtp-Source: AFSGD/Us3LiUCBRQwdlXyf77AZk+eLVcodSdMKMOtpWuCRoVM5lD+p1hzX6YKKdCBPs0e71d6JdM X-Received: by 2002:a62:1112:: with SMTP id z18mr6993877pfi.173.1543611727745; Fri, 30 Nov 2018 13:02:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1543611727; cv=none; d=google.com; s=arc-20160816; b=By1bJ8vSoqwOysdtdJ+c5Fopp324GVCec/o7SfAcxyn8amD9c2YHIhZvvi6weND83D OVlJS4vDXlJ5cQ0BcU8xy8EByEuDRLaF95xlChH7ELnYgVj+GQ7+tehTA149TaOGM0SK cwBOnaAkDuLPysNHEIqONPCwdx+yJm4BXOz6aSQ1nD3649OvsMMhDJBhSjTUfZ7aaqWj /EMbr57PC0m9YdGgm9kOkViT2n3RBS0zEBw7Ha1MjotUeygLUiL/pyGvp21LXUz/rL/k 4+bYoPkR/wZXtMDL1sw9flQLKaFIwNuiKQeJiVfGqbyTdn6HHSr98nah8uo9TdtRSxJc hUMA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=t28DaIJx46kC4lrRXQsurLwY9/AiVu9YI/wsKmp3Hpo=; b=gedkAzvcauCbcCHBUsdBqgh0FiOZ8j4PADMNXFAwjg/qyiC5Je9FsBenSDE3QGRKF0 lX+Q59z0MB8GGkaQKz6acw/kTnudKLPR449CjIYZ+cehB/RFc2GjtxDHx+zIVgH6OfV+ rDnGzcvrKoQwbkKExIR/Hxa8r20TuZUfpqhlGhz5xm4x+R8mUcx2Gef3RAOiE68qXByx MwoJTNkJbflFVqOhO8HujtuKXM4Go7eXlBQUKTmmEF5oBUXjk0mE5uXnP+MleCxZOBv5 8k1xFIUAXdrNyxf/xlLqqbF4MgX0PO6zCDF8qFF2aSqfER37TcFiD8a8yvQGZoWGpP7X W4FQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=hsb1y5qK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t136si7026720pfc.262.2018.11.30.13.01.52; Fri, 30 Nov 2018 13:02:07 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=hsb1y5qK; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726728AbeLAIKY (ORCPT + 99 others); Sat, 1 Dec 2018 03:10:24 -0500 Received: from mail.kernel.org ([198.145.29.99]:37374 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725867AbeLAIKY (ORCPT ); Sat, 1 Dec 2018 03:10:24 -0500 Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com [209.85.128.54]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A1CC821479 for ; Fri, 30 Nov 2018 20:59:50 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1543611590; bh=dklhLqSh/R3eawAshrdGCTAzouty0hE7j0furIEfWGM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=hsb1y5qKkN4Q39SDlL0Ot+tNE3SGupkh0uvX/i4BHmbq/iUg5dHQ5IdYTHnwvX9p1 wPyu++1o4NKRoGRxlVoc6mmup5vHLwXttrvgvprfD7lTwn7Qn99mu7nELLkeepbF9x 7Fv/ZvPo93q4uEmK4CSu1Pp+r5rB7DeHUfrfHjRo= Received: by mail-wm1-f54.google.com with SMTP id n133so248572wmd.4 for ; Fri, 30 Nov 2018 12:59:50 -0800 (PST) X-Gm-Message-State: AA+aEWZJHUnzFcAN86tXF/ZzMj8h7DD/xV2bOOWqURVqDC8fAZlHbza1 7DH6ZivcTloMthZWppwg96UZp9daDH7X0PmSmhGc0A== X-Received: by 2002:a1c:b1d5:: with SMTP id a204mr284175wmf.32.1543611589060; Fri, 30 Nov 2018 12:59:49 -0800 (PST) MIME-Version: 1.0 References: <20181129124404.2fe55dd0@gandalf.local.home> <20181129125857.75c55b96@gandalf.local.home> <20181129134725.6d86ade6@gandalf.local.home> <20181129202452.56f4j2wdct6qbaqo@treble> <20181130183917.hxmti5josgq4clti@treble> <20181130152852.456ce379@gandalf.local.home> In-Reply-To: <20181130152852.456ce379@gandalf.local.home> From: Andy Lutomirski Date: Fri, 30 Nov 2018 12:59:36 -0800 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 4/4] x86/static_call: Add inline static call implementation for x86-64 To: Steven Rostedt Cc: Andrew Lutomirski , Linus Torvalds , Josh Poimboeuf , Peter Zijlstra , X86 ML , LKML , Ard Biesheuvel , Ingo Molnar , Thomas Gleixner , Masami Hiramatsu , Jason Baron , Jiri Kosina , David Laight , Borislav Petkov , julia@ni.com, jeyu@kernel.org, "H. Peter Anvin" 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 Fri, Nov 30, 2018 at 12:28 PM Steven Rostedt wrote: > > On Fri, 30 Nov 2018 12:18:33 -0800 > Andy Lutomirski wrote: > > > Or we could replace that IPI with x86's bona fide serialize-all-cpus > > primitive and then we can just retry instead of emulating. It's a > > piece of cake -- we just trigger an SMI :) /me runs away. > > I must have fallen on my head one too many times, because I really like > the idea of synchronizing all the CPUs with an SMI! (If that's even > possible). The IPI's that are sent are only to force smp_mb() on all > CPUs. Which should be something an SMI could do. > > /me runs after Andy According to the SDM, you can program the APIC ICR to request an SMI. It's not remotely clear to me what will happen if we do this. For all I know, the SMI handler will explode and the computer will catch fire. PeterZ?