Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp1122055imm; Wed, 26 Sep 2018 12:03:19 -0700 (PDT) X-Google-Smtp-Source: ACcGV63jX6haDUchAl6IPcEh40YyGfOM7TR6YcrRUL4dA/E4NVbhf+yzv+XPHFG/KUpysgCSmxyY X-Received: by 2002:a62:6b41:: with SMTP id g62-v6mr7704074pfc.113.1537988599568; Wed, 26 Sep 2018 12:03:19 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1537988599; cv=none; d=google.com; s=arc-20160816; b=b6pq5vSsr6hIoBTYv4P08xvAcH90NQ4G2Nn5muRiiL7LmI7HCpgHQyqzyxSmMsrFB5 7DvLOkSXqn8MahFnopbWh2iL3Ryhc3+V0P891CQ138OLjaym/GHGsz1z+g/m1mVC2xqe 0G9AbfLwBecFNAEW7lcUBGeqZV8vND9554GON9oUifujlxow8icLb5qqV9sSFatQ1H4M qmSFpk/9j+YtySI5VQS9KvtV4fkf4BMzyvRewoTperTiQEgOVyPSAc90H0KVH6AtWJ0U h1/chg6n3P1uBiK5DA5RGxYVjMQ8eTrKpbU3cQzRTpHKkYRnFR6afFhY5rkiQ8ZwZJZO q2FA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=9+tNMKJYqTY43lyd7oCacMwqwn+AIFGayvCdw+NFT1o=; b=tDaT0CV/EWzxMx3nbvP6fw9Fnu/5DuLiRANU+Q6SmxLhcYyFW6EMrmJLErxVhAmfn0 psU9QJZQ/Ss6pTJVskoX+WwkKsLwPdGRKLq21Cvcsl40wvrpnMz5KKtAhiPBOr+4kk7F lRCgFy8gFi5I+UGPnQXPjq0O46Mdv42LheJzjD/Lhiy69sPT4fhJK5w+63zo7q8nInYw z5L6F9Fl6sPUEDUm+Joe+xr6k1HEDXiic3LTT8vMgH02isDuxt/3AUtN4hZpJYCub7Yn 53z9lcIpzmkld8rkZ0QH7MAkbdanKQFAPCmTIV22uJjpE7+BdhAhd2M9ypvc5juSggQv KlKg== 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 a64-v6si5371484pfb.224.2018.09.26.12.03.03; Wed, 26 Sep 2018 12:03:19 -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 S1728557AbeI0BPF (ORCPT + 99 others); Wed, 26 Sep 2018 21:15:05 -0400 Received: from mga04.intel.com ([192.55.52.120]:64733 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725848AbeI0BPF (ORCPT ); Wed, 26 Sep 2018 21:15:05 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga008.jf.intel.com ([10.7.209.65]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Sep 2018 12:00:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,307,1534834800"; d="scan'208";a="76436979" Received: from rchatre-s.jf.intel.com ([10.54.70.76]) by orsmga008.jf.intel.com with ESMTP; 26 Sep 2018 12:00:39 -0700 From: Reinette Chatre To: tglx@linutronix.de, fenghua.yu@intel.com, tony.luck@intel.com Cc: jithu.joseph@intel.com, gavin.hindman@intel.com, dave.hansen@intel.com, mingo@redhat.com, hpa@zytor.com, x86@kernel.org, linux-kernel@vger.kernel.org, Reinette Chatre Subject: [PATCH 0/3] x86/intel_rdt: Fix exclusive mode with CDP resources Date: Wed, 26 Sep 2018 11:59:42 -0700 Message-Id: X-Mailer: git-send-email 2.17.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Dear Maintainers, CDP resources do not currently behave as expected when there are resource groups with mode 'exclusive'. In the example below it was possible to create two resource groups, p1 and p2, that are both in exclusive mode but their usage of the underlying L2 cache actually overlaps. root@glk:/sys/fs/resctrl# ls cpus cpus_list info mode p1 p2 schemata size tasks root@glk:/sys/fs/resctrl# cat schemata L2DATA:0=fff0 L2CODE:0=fff0 root@glk:/sys/fs/resctrl# cat mode shareable root@glk:/sys/fs/resctrl# cat p1/schemata L2DATA:0=0003 L2CODE:0=000c root@glk:/sys/fs/resctrl# cat p1/mode exclusive root@glk:/sys/fs/resctrl# cat p2/schemata L2DATA:0=000c L2CODE:0=0003 root@glk:/sys/fs/resctrl# cat p2/mode exclusive root@glk:/sys/fs/resctrl# cat info/L2CODE/bit_usage 0=SSSSSSSSSSSSEEEE root@glk:/sys/fs/resctrl# cat info/L2DATA/bit_usage 0=SSSSSSSSSSSSEEEE root@glk:/sys/fs/resctrl# In the above example, the CBM of L2DATA in p1 overlaps with the CBM of L2CODE in p2 while they are both in exclusive mode. While it may reflect no overlap among the L2DATA resources specifically it does actually imply overlap of use of the underlying hardware that is not the intention of 'exclusive' mode. This happens because the current implementation treats L2CODE and L2DATA as totally independent, when it is actually referring to the same underlying hardware. This series fixes the potential for overlap of hardware resource use when resource groups are in 'exclusive' mode by ensuring that if there is a CDP peer on the same hardware then any overlap test would consider it also. Allocations of data and code resources within the same exclusive resource group are allowed to overlap. Your feedback will be greatly appreciated. Reinette Reinette Chatre (3): x86/intel_rdt: Introduce utility to obtain CDP peer x86/intel_rdt: CBM overlap should also check for overlap with CDP peer x86/intel_rdt: Fix initial allocation to consider CDP arch/x86/kernel/cpu/intel_rdt_rdtgroup.c | 133 ++++++++++++++++++++++- 1 file changed, 128 insertions(+), 5 deletions(-) -- 2.17.0