Received: by 10.223.185.116 with SMTP id b49csp4286874wrg; Mon, 19 Feb 2018 15:01:58 -0800 (PST) X-Google-Smtp-Source: AH8x226jf7arQdQnzSkRfaqixhCnfv8q1bPBoAhXiJLZ/uBNlc8P40OUpp03yjUe+aSnOzbDOGpL X-Received: by 2002:a17:902:9306:: with SMTP id bc6-v6mr15398279plb.29.1519081317896; Mon, 19 Feb 2018 15:01:57 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1519081317; cv=none; d=google.com; s=arc-20160816; b=VO//enelIHWug2cfgmOs1H8MtfhMzuQ/h57LCZK0rUkiob+i2UL6v0RgMftUJGT0NP YPtfZFAkDycW72f0hnx7i3nr7U+TS54hN7aoJlEqx6VjwtavOp1u8d2uViCv+wzIF9TE UPAppH5jtjFE1uH6PhcvVXMxOb31yXtd1/64M1nFuctFbvp07XzANAAGKuYLzQGYV/PS Q6pJ0CzBX2cO61vSQFRLacrRRLJDB+zGim90kFGinxfCA4RxaCglT7nWU9y4ALHuXCP9 lPdnj2a8dppK//voT/sD0pObljGZyOSbuYDLOhfbqnMJs09lhNt/doiS/wo5LF+CwlZO 75nA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=6+zFbbaFvAzjPTu7EaVPhjB2Yeoz9pRpO4mFI1TNBLM=; b=OHa0qeuZ+27fQSo1UR3cJs10AzWV6C2rqwGWvsLW0Z89iAtpnMLtsKYSs19KWuiJLN TkDlEvvADVUjLplz3HiGjNuWSxTNRBdOz+ibcPU/6hzTQ88vRBf2rzsKRMSw2a18nhu1 vsu5fM+B/8ZoxxUrwfi4auUgfDE5L5KWi/n2YXvxJPnowwUKGzufYUa0ykboZR0OJM0f ZbyWVe6+jS8tJAQk+5pQHoyop8GwMMNIwaE4/1zpKumnlMnK9Mgl3g9sBhSqelNmkxYh c7oKTGdGUohIWrKLNuiab6z+kKj99npYlDX5/CJeQU944DNAKKG30VHIGeBiEDvMdO20 4kMQ== 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 m11-v6si5341587pln.320.2018.02.19.15.01.43; Mon, 19 Feb 2018 15:01:57 -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 S932339AbeBSXAW (ORCPT + 99 others); Mon, 19 Feb 2018 18:00:22 -0500 Received: from mga01.intel.com ([192.55.52.88]:17575 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932169AbeBSXAU (ORCPT ); Mon, 19 Feb 2018 18:00:20 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Feb 2018 15:00:18 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.46,537,1511856000"; d="scan'208";a="19314940" Received: from rchatre-mobl.amr.corp.intel.com (HELO [10.255.73.9]) ([10.255.73.9]) by orsmga008.jf.intel.com with ESMTP; 19 Feb 2018 15:00:17 -0800 Subject: Re: [RFC PATCH V2 11/22] x86/intel_rdt: Associate pseudo-locked regions with its domain To: Thomas Gleixner 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 References: <216ad1ef8314dc578a900ff8b06248464f5aa2ee.1518443616.git.reinette.chatre@intel.com> From: Reinette Chatre Message-ID: <7bd1f8e8-116f-bdb2-23d2-a94f9a21e028@intel.com> Date: Mon, 19 Feb 2018 15:00:17 -0800 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. > >> 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. Will fix. Reinette