Received: by 10.223.185.116 with SMTP id b49csp2790wrg; Mon, 19 Feb 2018 15:20:38 -0800 (PST) X-Google-Smtp-Source: AH8x2243IznnP5WmqrKTEoZ1muPb3q3edZVmYS4RRaawLk5XiIgB6PX1j0tBo/8j0EkOMFdNiPTU X-Received: by 2002:a17:902:5a88:: with SMTP id r8-v6mr16164864pli.426.1519082438814; Mon, 19 Feb 2018 15:20:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519082438; cv=none; d=google.com; s=arc-20160816; b=q6FG0ERd58HHo+LSF28KnEZsSTNWyZ7nMTmf8Hd+TaypUlMlYU1GrY+u45NWnLXA+a YGJphOCrYQT2i72oa2FShLNumP+WKMcAM9/4yJbsqh2O4AM51YRmtnGdYUFJvo3OkHr7 wQQdRdN+hYwIK4s17dMn48o+cq5avSC0blO1daDJgFmChitJQe+2ub7AgFDJpZ9Cpm9Y gBxprQF1W+NMl2Xws2rDCQKEOId60VOmaqB8lYTPNVLt6yaqMnUWEpnSimBli35Nww4B HjInaQ0zhXSVtGS+Ff7VJth2iubxTsHUt8Y8tXpekOUVtd32VAVQt/OdZrjKZCN8acfY XIwg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=hbKBr8y2YVIaKTi/VoN/tN61J72F20f/53f29eIfFX4=; b=zN4zSqikDEt7tfBfEgT4Ue3wHjK7RAWIrylHX1wqTDU6+XYB+rwl1C3ptYjftO+DpG AU2FbIYUnAnhS6+N/v2xM4qqP8keHU/w+Bt++cpyhp816l0NAl4+QJ8ZFatkd9v3X/CE Sv13f877DPwjOb9Sx9U7YBYQM1gv41EUucAO1CIs/o0VUlXsdci+dC5ay5vln9Yu0Clm j7cpQPiPpeDAVwaSIvcJVtc6zdjSSF+DmLit8TvEB8BLwp83AA85JRgUqGkT7SYDyJep JN2FhE3Qn7MvWV2E5WYsNczEWESrcwX4zDNXO9qHyVKFF7N3tE+gPopRSVcFCG8gIKR2 BJsQ== ARC-Authentication-Results: i=1; mx.google.com; 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 d81si10170966pfd.139.2018.02.19.15.20.24; Mon, 19 Feb 2018 15:20:38 -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; 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 S932242AbeBSXTq (ORCPT + 99 others); Mon, 19 Feb 2018 18:19:46 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:60419 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932169AbeBSXTp (ORCPT ); Mon, 19 Feb 2018 18:19:45 -0500 Received: from [37.81.189.72] by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1enufP-0005bT-EI; Tue, 20 Feb 2018 00:16:15 +0100 Date: Tue, 20 Feb 2018 00:19:49 +0100 (CET) From: Thomas Gleixner To: Reinette Chatre cc: fenghua.yu@intel.com, tony.luck@intel.com, gavin.hindman@intel.com, vikas.shivappa@linux.intel.com, dave.hansen@intel.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain In-Reply-To: <7bd1f8e8-116f-bdb2-23d2-a94f9a21e028@intel.com> Message-ID: References: <216ad1ef8314dc578a900ff8b06248464f5aa2ee.1518443616.git.reinette.chatre@intel.com> <7bd1f8e8-116f-bdb2-23d2-a94f9a21e028@intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 19 Feb 2018, Reinette Chatre wrote: > Hi Thomas, > > On 2/19/2018 1:19 PM, Thomas Gleixner wrote: > > On Tue, 13 Feb 2018, Reinette Chatre wrote: > > > >> After a pseudo-locked region is locked it needs to be associated with > >> the RDT domain representing the pseudo-locked cache so that its life > >> cycle can be managed correctly. > >> > >> Only a single pseudo-locked region can exist on any cache instance so we > >> maintain a single pointer to a pseudo-locked region from each RDT > >> domain. > > > > Why is only a single pseudo locked region possible? > > The setup of a pseudo-locked region requires the usage of wbinvd. If a > second pseudo-locked region is thus attempted it will evict the > pseudo-locked data of the first. Why does it neeed wbinvd? wbinvd is a big hammer. What's wrong with clflush? Thanks, tglx