Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1079481ybl; Wed, 28 Aug 2019 09:19:44 -0700 (PDT) X-Google-Smtp-Source: APXvYqyiG93wcOP1FP/opvGaPTSIx5M8QpA4rr4YUSybsogQQnCTgiJeO6k8ahNxqGgYDmDIeNJT X-Received: by 2002:a63:5f01:: with SMTP id t1mr3820604pgb.200.1567009183881; Wed, 28 Aug 2019 09:19:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567009183; cv=none; d=google.com; s=arc-20160816; b=KHKxisBKfcAqFvaoIsxaKidSlu8fpZBuLztOyr+qURCj8LxWKx4DRnIVBvaRAM6OcW /qrPxvequDIhxmNnadPMLijj+sx9uKZfZPISPKrcTvNMDtw9U32p/tZEbvLMz2a6vshG 7mPy6nok23gPevBpXTSf33fBmf4YA7mmU4AvExzn3CEDtVqt/Hv0RoIKdJmeKoZpbT13 mR52QD/Y+VCn3NwXiRzgSdMp/+rlxYDA1aJ/gWERB8oMA3eSVh1N8gl7q8TMJ21TaOb1 VH3+WsKl6C+rLkQPMcUfOVGTVJX3QbnyL5intFkCFL1+MtAK75SMW4496SQsKDhIYRoW ipow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=ICJAa08tadoxVPLwvjSEX3IwJxKlsW5cqkoOWAu/x8M=; b=LDC4+VECaznq3BC79/7zh3kjqf94/VnNn97LZNK+k+eE2fo4EKetDjw8xPqK44RHOP WUjFGfW27Gh2CqQnoQ1i0JcyYocbmBXU5xvr9RlQeeoFrqnQC0L0LCM+r5wdTwHf1xU/ P1JE26Kvp58fp/KRUCcmHBoZEmXtFAIgQlGG20Da389xRjAY5f7ASHX2AqB1nkbFIENQ huhzDrdI8SfvtDrAO++vkNYxXNYnNNn80QL2Yhl7c4kAlQKBZzh+DbTDCRgXUSAm1TYx fOHRhJzYN6geiSSJ0oSo9OmCTrbhwcSjw2HVlHItk67Q8xv/wtFfhclaHz/DDkvwHzlQ +b/A== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=DESqQHh2; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g62si2955364pfb.219.2019.08.28.09.19.27; Wed, 28 Aug 2019 09:19:43 -0700 (PDT) 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=fail header.i=@infradead.org header.s=bombadil.20170209 header.b=DESqQHh2; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726561AbfH1QQ6 (ORCPT + 99 others); Wed, 28 Aug 2019 12:16:58 -0400 Received: from bombadil.infradead.org ([198.137.202.133]:33684 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726395AbfH1QQ5 (ORCPT ); Wed, 28 Aug 2019 12:16:57 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=bombadil.20170209; h=In-Reply-To:Content-Type:MIME-Version :References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ICJAa08tadoxVPLwvjSEX3IwJxKlsW5cqkoOWAu/x8M=; b=DESqQHh2cNViea0m7r8+H3fu4 1dFucgAEMAvngpKuOByQxETWWcVYF63MS9s/79ByDMlJnv6qVLGka3yxIR5TK2iA2KU5rmNEouNTS 8NG7VowmDv2KNIew7s0qLUb9qUexQOyNvqDGS/eCN0echuCOdJRrn6xZCsZqW/jRAzw4oSJTmHbmh kr117gOELOdhx6Xo3ultpIVg5PbXH/2dYFYcUwdVWshiYLPYs+FLR93/QefbbERy+AcAP1Z0nyMqL p6rJekQVD/8egGLC9IiSLimuDDhsZq60Y64g0+47/xSF8wFIaBHaZcl6/n7GTzfTu0Qfut1ZPb1fC 1nb2DF8iA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=noisy.programming.kicks-ass.net) by bombadil.infradead.org with esmtpsa (Exim 4.92 #3 (Red Hat Linux)) id 1i30cm-0005WW-LX; Wed, 28 Aug 2019 16:16:44 +0000 Received: from hirez.programming.kicks-ass.net (hirez.programming.kicks-ass.net [192.168.1.225]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by noisy.programming.kicks-ass.net (Postfix) with ESMTPS id EA2C1307594; Wed, 28 Aug 2019 18:16:07 +0200 (CEST) Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id E174C20230B32; Wed, 28 Aug 2019 18:16:41 +0200 (CEST) Date: Wed, 28 Aug 2019 18:16:41 +0200 From: Peter Zijlstra To: Tim Chen Cc: Matthew Garrett , Vineeth Remanan Pillai , Nishanth Aravamudan , Julien Desfossez , mingo@kernel.org, tglx@linutronix.de, pjt@google.com, torvalds@linux-foundation.org, linux-kernel@vger.kernel.org, subhra.mazumdar@oracle.com, fweisbec@gmail.com, keescook@chromium.org, kerrnel@google.com, Phil Auld , Aaron Lu , Aubrey Li , Valentin Schneider , Mel Gorman , Pawan Gupta , Paolo Bonzini Subject: Re: [RFC PATCH v3 00/16] Core scheduling v3 Message-ID: <20190828161641.GJ2369@hirez.programming.kicks-ass.net> References: <20190827211417.snpwgnhsu5t6u52y@srcf.ucam.org> <20190827215035.GH2332@hirez.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Aug 28, 2019 at 08:59:21AM -0700, Tim Chen wrote: > On 8/27/19 2:50 PM, Peter Zijlstra wrote: > > On Tue, Aug 27, 2019 at 10:14:17PM +0100, Matthew Garrett wrote: > >> Apple have provided a sysctl that allows applications to indicate that > >> specific threads should make use of core isolation while allowing > >> the rest of the system to make use of SMT, and browsers (Safari, Firefox > >> and Chrome, at least) are now making use of this. Trying to do something > >> similar using cgroups seems a bit awkward. Would something like this be > >> reasonable? > > > > Sure; like I wrote earlier; I only did the cgroup thing because I was > > lazy and it was the easiest interface to hack on in a hurry. > > > > The rest of the ABI nonsense can 'trivially' be done later; if when we > > decide to actually do this. > > > > And given MDS, I'm still not entirely convinced it all makes sense. If > > it were just L1TF, then yes, but now... > > > > For MDS, core-scheduler does prevent thread to thread > attack between user space threads running on sibling CPU threads. > Yes, it doesn't prevent the user to kernel attack from sibling > which will require additional mitigation measure. However, it does > block a major attack vector for MDS if HT is enabled. I'm not sure what your argument is; the dike has two holes; you plug one, you still drown.