Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753225AbeADUja (ORCPT + 1 other); Thu, 4 Jan 2018 15:39:30 -0500 Received: from mx2.suse.de ([195.135.220.15]:45565 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753154AbeADUj2 (ORCPT ); Thu, 4 Jan 2018 15:39:28 -0500 Date: Thu, 4 Jan 2018 21:39:24 +0100 (CET) From: Jiri Kosina To: Alan Cox cc: Pavel Machek , Linus Torvalds , Dan Williams , Linux Kernel Mailing List , Mark Rutland , linux-arch@vger.kernel.org, Peter Zijlstra , Greg KH , Thomas Gleixner , Elena Reshetova Subject: Re: [RFC PATCH] asm/generic: introduce if_nospec and nospec_barrier In-Reply-To: <20180104203246.5ff65328@alans-desktop> Message-ID: References: <20180103223827.39601-1-mark.rutland@arm.com> <151502463248.33513.5960736946233335087.stgit@dwillia2-desk3.amr.corp.intel.com> <20180104010754.22ca6a74@alans-desktop> <20180104014100.3786e686@alans-desktop> <20180104193936.GB10427@amd> <20180104203246.5ff65328@alans-desktop> User-Agent: Alpine 2.21 (LSU 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Return-Path: On Thu, 4 Jan 2018, Alan Cox wrote: > You never go from one user process to another except via the kernel. We > have no hardware scheduling going on. That means that if the kernel > and/or CPU imposes the correct speculation barriers you can't attack > anyone but yourself. So how does this work on HT with the shared BTB? There is no context switch (and hence no IBPB) happening between the threads sharing it. -- Jiri Kosina SUSE Labs