From patchwork Tue Aug 1 08:48:54 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Sun X-Patchwork-Id: 9873901 Return-Path: Received: from mail.wl.linuxfoundation.org (pdx-wl-mail.web.codeaurora.org [172.30.200.125]) by pdx-korg-patchwork.web.codeaurora.org (Postfix) with ESMTP id EC7AB603B4 for ; Tue, 1 Aug 2017 09:07:13 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 009AE2582C for ; Tue, 1 Aug 2017 09:07:14 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id E97D728670; Tue, 1 Aug 2017 09:07:13 +0000 (UTC) X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on pdx-wl-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.2 required=2.0 tests=BAYES_00, RCVD_IN_DNSWL_MED autolearn=ham version=3.3.1 Received: from lists.xenproject.org (lists.xenproject.org [192.237.175.120]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.wl.linuxfoundation.org (Postfix) with ESMTPS id 6425527F91 for ; Tue, 1 Aug 2017 09:07:13 +0000 (UTC) Received: from localhost ([127.0.0.1] helo=lists.xenproject.org) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcT77-0005yz-Nm; Tue, 01 Aug 2017 09:05:17 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcT76-0005wY-Je for xen-devel@lists.xenproject.org; Tue, 01 Aug 2017 09:05:16 +0000 Received: from [85.158.139.211] by server-9.bemta-5.messagelabs.com id DE/AA-01994-B4440895; Tue, 01 Aug 2017 09:05:15 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrLLMWRWlGSWpSXmKPExsXS1tYhouvt0hB pMHGhpMX3LZOZHBg9Dn+4whLAGMWamZeUX5HAmrHgw0bmgguaFavWcTYwXlHqYuTiEBKYxijx 6fgJti5GTg4JAV6JI8tmsELY/hLzvs0Cs4UEGhgl1p4rALHZBNQlHn/tYQKxRQSUJO6tmswEM ohZ4DCTxPVbX8AahAUcJC687gOyOThYBFQl9v3zBgnzCnhIvL7cxQIxX07i5LHJYOWcQPEdN2 8wg5QLCbhL7JyZOIGRdwEjwypG9eLUorLUIl1TvaSizPSMktzEzBxdQwNTvdzU4uLE9NScxKR iveT83E2MwEBgAIIdjF/6nQ8xSnIwKYnyKvbURwrxJeWnVGYkFmfEF5XmpBYfYpTh4FCS4JVw bogUEixKTU+tSMvMAYYkTFqCg0dJhPeCE1Cat7ggMbc4Mx0idYrRmGPD6vVfmDheTfj/jUmIJ S8/L1VKnPciSKkASGlGaR7cIFisXGKUlRLmZQQ6TYinILUoN7MEVf4VozgHo5IwryzIPTyZeS Vw+14BncIEdIpkaS3IKSWJCCmpBsalK5k03+/bskfnVfe2hbs/it4P0BeqZZ9YN/OiCEf23C2 xvw2urJ6j86lquYrXWm6Ng54JHxeI3TqYwbfftO3xQilXRp6MBbwLQ3ZvudC55HFB7+/elSIx +694yhXe2DrjXr64YRHLml0P5m9cX254dsKMea/4bV+whVkIN9fem2AVvorbXTBdiaU4I9FQi 7moOBEAr0lL4JACAAA= X-Env-Sender: yi.y.sun@linux.intel.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1501578248!89431283!24 X-Originating-IP: [134.134.136.20] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTM0LjEzNC4xMzYuMjAgPT4gMzU1MzU4\n X-StarScan-Received: X-StarScan-Version: 9.4.25; banners=-,-,- X-VirusChecked: Checked Received: (qmail 58443 invoked from network); 1 Aug 2017 09:05:14 -0000 Received: from mga02.intel.com (HELO mga02.intel.com) (134.134.136.20) by server-16.tower-206.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 1 Aug 2017 09:05:14 -0000 Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Aug 2017 02:05:14 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,305,1498546800"; d="scan'208";a="118061882" Received: from vmmmba-s2600wft.bj.intel.com ([10.240.193.80]) by orsmga002.jf.intel.com with ESMTP; 01 Aug 2017 02:05:11 -0700 From: Yi Sun To: xen-devel@lists.xenproject.org Date: Tue, 1 Aug 2017 16:48:54 +0800 Message-Id: <1501577334-7431-24-git-send-email-yi.y.sun@linux.intel.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1501577334-7431-1-git-send-email-yi.y.sun@linux.intel.com> References: <1501577334-7431-1-git-send-email-yi.y.sun@linux.intel.com> Cc: kevin.tian@intel.com, wei.liu2@citrix.com, andrew.cooper3@citrix.com, dario.faggioli@citrix.com, He Chen , ian.jackson@eu.citrix.com, Yi Sun , mengxu@cis.upenn.edu, jbeulich@suse.com, chao.p.peng@linux.intel.com, roger.pau@citrix.com Subject: [Xen-devel] [PATCH v15 23/23] docs: add L2 CAT description in docs. X-BeenThere: xen-devel@lists.xen.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Xen developer discussion List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" X-Virus-Scanned: ClamAV using ClamSMTP This patch adds L2 CAT description in related documents. Signed-off-by: He Chen Signed-off-by: Yi Sun Acked-by: Wei Liu --- v13: - rebase the patch on latest code. --- docs/man/xl.pod.1.in | 27 +++++++++++++++++++++++---- docs/misc/xl-psr.markdown | 18 ++++++++++++------ 2 files changed, 35 insertions(+), 10 deletions(-) diff --git a/docs/man/xl.pod.1.in b/docs/man/xl.pod.1.in index d87fe16..16c8306 100644 --- a/docs/man/xl.pod.1.in +++ b/docs/man/xl.pod.1.in @@ -1712,6 +1712,9 @@ occupancy monitoring share the same set of underlying monitoring service. Once a domain is attached to the monitoring service, monitoring data can be shown for any of these monitoring types. +There is no cache monitoring and memory bandwidth monitoring on L2 cache so +far. + =over 4 =item B I @@ -1736,7 +1739,7 @@ monitor types are: Intel Broadwell and later server platforms offer capabilities to configure and make use of the Cache Allocation Technology (CAT) mechanisms, which enable more -cache resources (i.e. L3 cache) to be made available for high priority +cache resources (i.e. L3/L2 cache) to be made available for high priority applications. In the Xen implementation, CAT is used to control cache allocation on VM basis. To enforce cache on a specific domain, just set capacity bitmasks (CBM) for the domain. @@ -1746,11 +1749,11 @@ Intel Broadwell and later server platforms also offer Code/Data Prioritization applications. CDP is used on a per VM basis in the Xen implementation. To specify code or data CBM for the domain, CDP feature must be enabled and CBM type options need to be specified when setting CBM, and the type options (code -and data) are mutually exclusive. +and data) are mutually exclusive. There is no CDP support on L2 so far. =over 4 -=item B [I] I I +=item B [I] I I Set cache capacity bitmasks(CBM) for a domain. For how to specify I please refer to L. @@ -1763,6 +1766,11 @@ B Specify the socket to process, otherwise all sockets are processed. +=item B<-l LEVEL>, B<--level=LEVEL> + +Specify the cache level to process, otherwise the last level cache (L3) is +processed. + =item B<-c>, B<--code> Set code CBM when CDP is enabled. @@ -1773,10 +1781,21 @@ Set data CBM when CDP is enabled. =back -=item B [I] +=item B [I] [I] Show CAT settings for a certain domain or all domains. +B + +=over 4 + +=item B<-l LEVEL>, B<--level=LEVEL> + +Specify the cache level to process, otherwise the last level cache (L3) is +processed. + +=back + =back =head1 IGNORED FOR COMPATIBILITY WITH XM diff --git a/docs/misc/xl-psr.markdown b/docs/misc/xl-psr.markdown index c3c1e8e..04dd957 100644 --- a/docs/misc/xl-psr.markdown +++ b/docs/misc/xl-psr.markdown @@ -70,7 +70,7 @@ total-mem-bandwidth instead of cache-occupancy). E.g. after a `xl psr-cmt-attach Cache Allocation Technology (CAT) is a new feature available on Intel Broadwell and later server platforms that allows an OS or Hypervisor/VMM to -partition cache allocation (i.e. L3 cache) based on application priority or +partition cache allocation (i.e. L3/L2 cache) based on application priority or Class of Service (COS). Each COS is configured using capacity bitmasks (CBM) which represent cache capacity and indicate the degree of overlap and isolation between classes. System cache resource is divided into numbers of @@ -107,7 +107,7 @@ System CAT information such as maximum COS and CBM length can be obtained by: The simplest way to change a domain's CBM from its default is running: -`xl psr-cat-cbm-set [OPTIONS] ` +`xl psr-cat-set [OPTIONS] ` where cbm is a number to represent the corresponding cache subset can be used. A cbm is valid only when: @@ -119,13 +119,19 @@ A cbm is valid only when: In a multi-socket system, the same cbm will be set on each socket by default. Per socket cbm can be specified with the `--socket SOCKET` option. +In different systems, the different cache level is supported, e.g. L3 cache or +L2 cache. Per cache level cbm can be specified with the `--level LEVEL` option. + Setting the CBM may not be successful if insufficient COS is available. In such case unused COS(es) may be freed by setting CBM of all related domains to its default value(all-ones). Per domain CBM settings can be shown by: -`xl psr-cat-show` +`xl psr-cat-show [OPTIONS] ` + +In different systems, the different cache level is supported, e.g. L3 cache or +L2 cache. Per cache level cbm can be specified with the `--level LEVEL` option. ## Code and Data Prioritization (CDP) @@ -172,13 +178,13 @@ options is invalid. Example: Setting code CBM for a domain: -`xl psr-cat-cbm-set -c ` +`xl psr-cat-set -c ` Setting data CBM for a domain: -`xl psr-cat-cbm-set -d ` +`xl psr-cat-set -d ` Setting the same code and data CBM for a domain: -`xl psr-cat-cbm-set ` +`xl psr-cat-set ` ## Reference