Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp3806296imm; Tue, 29 May 2018 14:09:39 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL4X78kCpU51nva1fBl912NxPurlckwRp5hfZXBJro5VygIllRwa6cDUa6JZidjiuYX9Z9w X-Received: by 2002:a17:902:a586:: with SMTP id az6-v6mr55445plb.210.1527628179331; Tue, 29 May 2018 14:09:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1527628179; cv=none; d=google.com; s=arc-20160816; b=SAJC2GPnCE6ggylJ1kQL8k4sYbloEQdAdrfz2BjZYe41SUJDqqgTyWzk1QBSZaR/Zk AUMbgjf9x5gO5+lVwH0GFDgSy+BD6pUbHvbvbmG7pCHHZFlk0EgmwaodAcHDLVBjH1aY v+ZwzqbNMkoM6Br0LhYp+zQYekigYIU6o7Noqb8Yd23aJPDauryiZnUQQ+riYFH4ci07 rNcJPgmMzG9r+2/Gs+SVeDtbrSvkojKY6rS8zMxAcWnf58p7Z9SUkcbVCs2jJxY04Gji e5M3ERFLpiElhsDYUrxT8GjcbD9b+KDFGcxS2YRVyMCmyOCnE98k5D4FrXSISjrHpdBS h+nw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:references:in-reply-to:references :in-reply-to:message-id:date:subject:cc:to:from :arc-authentication-results; bh=iYaoC6RFqhXK+e98rR0HiyaBA7QqNkc+hFJ20yoTcTs=; b=1Af3xsmXymXOfiXbwdmwOWnfIjae0VWcA8QjLLS2DTQY++0C/cEgwiI5AYVD0+OEuv yML3OD6W2p52MUxHurI/auMiRz6j0KMDT3MIEcRT/RYXroZeFvQ1XNEsUKFzvimPXL8w luxOaoQH8KeWq4iZzMrxvK7Y+erCS0f0vmCD4MkLm9wVRVuBSdk7RVXnEQF0rlUAYyPT i2HLRspp+8ykJfo8F2bzWvVb4H0xkKgWCsEDL2syHSdeWDghpPf3+1Yn0bplLO3qJOQ9 44amp0zrQYjNBeFWVW5ODqmbwInfNiv8WqONbPtlNCEX79lHcc06DqtpF1t6eLAErNEB 3ZdQ== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f2-v6si26697380pgq.444.2018.05.29.14.09.25; Tue, 29 May 2018 14:09:39 -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; 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S967182AbeE2VGs (ORCPT + 99 others); Tue, 29 May 2018 17:06:48 -0400 Received: from mga14.intel.com ([192.55.52.115]:46449 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S937100AbeE2VA7 (ORCPT ); Tue, 29 May 2018 17:00:59 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 May 2018 14:00:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.49,457,1520924400"; d="scan'208";a="60127733" Received: from rchatre-s.jf.intel.com ([10.54.70.76]) by orsmga001.jf.intel.com with ESMTP; 29 May 2018 14:00:55 -0700 From: Reinette Chatre To: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com, vikas.shivappa@linux.intel.com Cc: gavin.hindman@intel.com, jithu.joseph@intel.com, dave.hansen@intel.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org, Reinette Chatre Subject: [PATCH V5 22/38] x86/intel_rdt: Add check to determine if monitoring in progress Date: Tue, 29 May 2018 05:57:47 -0700 Message-Id: X-Mailer: git-send-email 2.13.6 In-Reply-To: References: In-Reply-To: References: Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org When a resource group is pseudo-locked it is orphaned without a class of service associated with it. We thus do not want any monitoring in progress on a resource group that will be used for pseudo-locking. Introduce a test that can be used to determine if pseudo-locking in progress on a resource group. Temporarily mark it as unused to avoid compile warnings until it is used. Signed-off-by: Reinette Chatre --- arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c b/arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c index dc79b3090ac5..8693dbe602a2 100644 --- a/arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c +++ b/arch/x86/kernel/cpu/intel_rdt_pseudo_lock.c @@ -14,6 +14,19 @@ #include "intel_rdt.h" /** + * rdtgroup_monitor_in_progress - Test if monitoring in progress + * @r: resource group being queried + * + * Return: 1 if monitor groups have been created for this resource + * group, 0 otherwise. + */ +static int __attribute__ ((unused)) +rdtgroup_monitor_in_progress(struct rdtgroup *rdtgrp) +{ + return !list_empty(&rdtgrp->mon.crdtgrp_list); +} + +/** * rdtgroup_locksetup_user_restrict - Restrict user access to group * @rdtgrp: resource group needing access restricted * -- 2.13.6