From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Google-Smtp-Source: AH8x226VQg60KbXsyrjZ4wgiseNvzMWv+uRmDKgT59HiMjd/5mWX2071+JcPiv7LT2JR2+nuSXLL ARC-Seal: i=1; a=rsa-sha256; t=1517352228; cv=none; d=google.com; s=arc-20160816; b=b/11OpXxWber1/RpO0OY3p9FOBCimBkC1YrIy6TPXcUHySzLuBJIsjqAvD0nFMkrLB 6Ed9FQnVshEcLRv2jlcjs8OSXHvOeLKdRGaGrnTBMmvqg2+WdxVUI52XR3ZMhvnlWrS3 CMyeUk2ZlK9Ulb0dvCNgRhnHDShXfyeWa0HBbvMgNNZzMHDwnC6QtdaPW84GftabXx80 LVdz8FJZjjehEbIGqO9w1O3YD/fHCPRwMbVz84WJKLbjMtVAXcm2tx6XlnfVA4SHL2I/ XCTgqFv5mp41f1VsGuG6kFeXxvicKBgSkW949MMMfo/JrFH2CLT90acrKA5Kgw9qgKfT P/EQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:arc-authentication-results; bh=q5otL1bBbm18ht3nxDkEBA1Y+zzvUN+uDThmZosnJy0=; b=PA3I1wwPffKbbWG70pflZsN+a9tqmxU9dKRStpa1MG46A5eHPbruP33Y2rICl8MmZ+ soBj4E7j7szMAxgjzTwNFK7WTAjnO4juUNjsPlVwWB+OyAcrIzBZW5lQl7iXVEwr1AHp FC6tHloDIKB0T3oXBnU3cyvopQiMcfzfNKtYzH/RwXTlWMEVsIbZLoWEI+MWp9EV34cH if66bylLF3ZfaF3o7WHUnWoI0m3P1j3k3GsOAqoIjxJOcfOSZG2VDGkrYNDsnkek8Oq+ Oq6NiregJh7qAs8pTGgol4jUGvT/KMfMVS8X35Xg7duVpIWW3mM+eXTYbCDvAul/65c/ 3uEg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de Authentication-Results: mx.google.com; spf=pass (google.com: domain of bp@alien8.de designates 5.9.137.197 as permitted sender) smtp.mailfrom=bp@alien8.de Date: Tue, 30 Jan 2018 23:43:40 +0100 From: Borislav Petkov To: Tim Chen Cc: David Woodhouse , arjan@linux.intel.com, tglx@linutronix.de, karahmed@amazon.de, x86@kernel.org, linux-kernel@vger.kernel.org, peterz@infradead.org, pbonzini@redhat.com, ak@linux.intel.com, torvalds@linux-foundation.org, gregkh@linux-foundation.org, mingo@kernel.org, luto@kernel.org, linux@dominikbrodowski.net Subject: Re: [PATCH] x86/speculation: Use Indirect Branch Prediction Barrier in context switch Message-ID: <20180130224340.2zdfqttupugtqww5@pd.tnic> References: <1517263487-3708-1-git-send-email-dwmw@amazon.co.uk> <20180130203836.bsgme6kf6hstgbrx@pd.tnic> <024dd53b-1912-34fa-deb8-550c111df521@linux.intel.com> <20180130215731.pszc5u4gcc32ds4v@pd.tnic> <296de30b-515b-6eab-1b13-bb2f71451004@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <296de30b-515b-6eab-1b13-bb2f71451004@linux.intel.com> User-Agent: NeoMutt/20170609 (1.8.3) X-getmail-retrieved-from-mailbox: INBOX X-GMAIL-THRID: =?utf-8?q?1590966106432961445?= X-GMAIL-MSGID: =?utf-8?q?1591059130437160213?= X-Mailing-List: linux-kernel@vger.kernel.org List-ID: On Tue, Jan 30, 2018 at 02:26:53PM -0800, Tim Chen wrote: > If the process has multiple threads running on different cpus, I'm talking about issuing the barrier in set_dumpable(). What threads on multiple CPUs? -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.