Received: by 10.223.185.116 with SMTP id b49csp4213640wrg; Mon, 19 Feb 2018 13:21:35 -0800 (PST) X-Google-Smtp-Source: AH8x226qbs/R9PNGx4EfLeRBVdotPb75oGm89nrB3EMJHixFeVlK82AoymyooCzUA/t2ud48KNDE X-Received: by 10.101.77.201 with SMTP id q9mr6094391pgt.395.1519075295253; Mon, 19 Feb 2018 13:21:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519075295; cv=none; d=google.com; s=arc-20160816; b=dZ9pzFXdXrRjWixtpIVadFqN2Pfa4NJW4RYtXw814QRPTvNkp3ojP2mOFKbau1OBvk +9yDPO9dyun32RST7kJwYGOAUDE39afkfYEaWhHDOzwGrbSMsppi6wINS7mkFat5dv9/ TIlpYS66w8Xa1v6w/PyEG4mC4/sRf4u1PvOEm2UA5flJTFMe6icTTWGk71IKiGRd5wN9 DG2xA/C7FRlvJP4fvFTbYiLnjOltZ4Izzv9//MdazSiKwZ4rRJ6q2MeRERll/3UI/2WC 0iVAE6EXsP0acY5u5FdeuCgV8XwLNHguz0DiOKZ97gBbVDLxLTQaoLt7K2/MOSJ4LiI3 vtwQ== 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=98lreqGpfaPUiviRdG0KqKsP0koSey9tGOTlFkgM8cM=; b=Bhf/5X/jGF/LS/1zlZRRUeYtbn+kBBjxycO3T+c6lwOvXI1jATT4iIAiAea35EeHqj E9X/GavzsKqcugH+WBe0FpDWXCNedG65K8CjxauKWBAwRzihVhODFHoQVna5Ujc4EPQb sXAQWsKQyQDMIn/R3LsU73coznueqxM+Yk8lbr9bFPKXnG/YPX/mtJaWWMdl45M92PhQ EdLzsnqk3SajrNJ4ix2PGhwAe7URJGEVve9NQbBnzuDik7kHL/mtRueg8O0GPuVvnpEM BV5SJKDnvZyzog76urc6mBJNyjl8gBwVsbMzUSz5hXQA5qusHnRGRJVg0nGD3+rwIE+V hO7A== 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 z4-v6si1170833plo.57.2018.02.19.13.21.18; Mon, 19 Feb 2018 13:21:35 -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 S1753757AbeBSVUk (ORCPT + 99 others); Mon, 19 Feb 2018 16:20:40 -0500 Received: from Galois.linutronix.de ([146.0.238.70]:60265 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753676AbeBSVUj (ORCPT ); Mon, 19 Feb 2018 16:20:39 -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 1ensnM-0004OQ-Ta; Mon, 19 Feb 2018 22:16:21 +0100 Date: Mon, 19 Feb 2018 22:19:54 +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: <216ad1ef8314dc578a900ff8b06248464f5aa2ee.1518443616.git.reinette.chatre@intel.com> Message-ID: References: <216ad1ef8314dc578a900ff8b06248464f5aa2ee.1518443616.git.reinette.chatre@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 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? > Signed-off-by: Reinette Chatre > --- > arch/x86/kernel/cpu/intel_rdt.h | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/arch/x86/kernel/cpu/intel_rdt.h b/arch/x86/kernel/cpu/intel_rdt.h > index 060a0976ac00..f0e020686e99 100644 > --- a/arch/x86/kernel/cpu/intel_rdt.h > +++ b/arch/x86/kernel/cpu/intel_rdt.h > @@ -187,6 +187,8 @@ struct mbm_state { > u64 prev_msr; > }; > > +struct pseudo_lock_region; > + > /** > * struct rdt_domain - group of cpus sharing an RDT resource > * @list: all instances of this resource > @@ -205,6 +207,7 @@ struct mbm_state { > * @ctrl_val: array of cache or mem ctrl values (indexed by CLOSID) > * @new_ctrl: new ctrl value to be loaded > * @have_new_ctrl: did user provide new_ctrl for this domain > + * @plr: pseudo-locked region associated with this domain > */ > struct rdt_domain { > struct list_head list; > @@ -220,6 +223,7 @@ struct rdt_domain { > u32 *ctrl_val; > u32 new_ctrl; > bool have_new_ctrl; > + struct pseudo_lock_region *plr; Please keep the tabular fashion of the struct declaration intact. Thanks, tglx