From patchwork Thu Mar 16 11:08:15 2017 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Yi Sun X-Patchwork-Id: 9627901 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 68AA260522 for ; Thu, 16 Mar 2017 11:16:33 +0000 (UTC) Received: from mail.wl.linuxfoundation.org (localhost [127.0.0.1]) by mail.wl.linuxfoundation.org (Postfix) with ESMTP id 60D8C2857D for ; Thu, 16 Mar 2017 11:16:33 +0000 (UTC) Received: by mail.wl.linuxfoundation.org (Postfix, from userid 486) id 55CFF285A1; Thu, 16 Mar 2017 11:16:33 +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.1 required=2.0 tests=BAYES_00,DKIM_SIGNED, RCVD_IN_DNSWL_MED,T_DKIM_INVALID 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 CB58C285B5 for ; Thu, 16 Mar 2017 11:16:32 +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 1coTMo-0005M0-Gb; Thu, 16 Mar 2017 11:14:50 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1coTMn-0005JZ-FS for xen-devel@lists.xenproject.org; Thu, 16 Mar 2017 11:14:49 +0000 Received: from [85.158.137.68] by server-3.bemta-3.messagelabs.com id 18/41-14551-8A37AC85; Thu, 16 Mar 2017 11:14:48 +0000 X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDLMWRWlGSWpSXmKPExsVywNwkVndF8ak Ig2sXhSy+b5nM5MDocfjDFZYAxijWzLyk/IoE1owbb1oYC6aoV9zacZWpgfGwQhcjFweLwC0m iVcNC9lAHCGBaYwS5zatAnI4OSQEeCWOLJvBCmH7S7z81wpV1MAo0XRvPSNIgk1AXeLx1x4mE FtEQEni3qrJTCBFzAI7mSTWnf7ODJIQFrCX6H5ynQXEZhFQldg2uwVoKgcHr4CHxP2OCIgFch Inj00GW8YJFP7Y3g5mCwm4S7zb8Jd9AiPfAkaGVYwaxalFZalFuoYmeklFmekZJbmJmTm6hgb GermpxcWJ6ak5iUnFesn5uZsYgaHCAAQ7GFds9zzEKMnBpCTKW/7jRIQQX1J+SmVGYnFGfFFp TmrxIUYZDg4lCd4jSicjhASLUtNTK9Iyc4BBC5OW4OBREuHNBUnzFhck5hZnpkOkTjEqSonzX gBJCIAkMkrz4NpgkXKJUVZKmJcR6BAhnoLUotzMElT5V4ziHIxKwrybQabwZOaVwE1/BbSYCW jx2w8nQBaXJCKkpBoY5y/WyOpdUn3L0+nOz0layTvqZ9yYvHGP/Jw6Lbv13ior2oK5ry1XY7R L2tgrvUWaU0Z9TujrLRe/hdcdKJ/57Ew1S9z+eraq4MUqv6evkVrlPX35F5Vdbw9POz0tW2ah mWTmgy8PPr514HF9lWv4+ai8bWZWfc2XRj5/j6aoT5MZQgUVz0+aqsRSnJFoqMVcVJwIAMa/j oyPAgAA X-Env-Sender: yi.y.sun@linux.intel.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1489662818!78881615!24 X-Originating-IP: [192.55.52.93] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTkyLjU1LjUyLjkzID0+IDMyNDY2NQ==\n X-StarScan-Received: X-StarScan-Version: 9.2.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16370 invoked from network); 16 Mar 2017 11:14:47 -0000 Received: from mga11.intel.com (HELO mga11.intel.com) (192.55.52.93) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 16 Mar 2017 11:14:47 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intel.com; i=@intel.com; q=dns/txt; s=intel; t=1489662887; x=1521198887; h=from:to:cc:subject:date:message-id:in-reply-to: references; bh=EA2gHeotYpV/2UlvVU6TbnQ+xDfXvi+LYy93leg+rO4=; b=Pn6X/neGEQI41Lb/j6eRpNz/oVUoHx80m7xIjtu7rBIzieQMsuBfrHbH NIAe2K/F9m1TzWHv9cTcM2S8lkClGg==; Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 16 Mar 2017 04:14:47 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.36,172,1486454400"; d="scan'208";a="944976920" Received: from vmmmba-s2600wft.bj.intel.com ([10.240.193.63]) by orsmga003.jf.intel.com with ESMTP; 16 Mar 2017 04:14:44 -0700 From: Yi Sun To: xen-devel@lists.xenproject.org Date: Thu, 16 Mar 2017 19:08:15 +0800 Message-Id: <1489662495-5375-26-git-send-email-yi.y.sun@linux.intel.com> X-Mailer: git-send-email 1.9.1 In-Reply-To: <1489662495-5375-1-git-send-email-yi.y.sun@linux.intel.com> References: <1489662495-5375-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@linux.intel.com, 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 v9 25/25] 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 --- docs/man/xl.pod.1.in | 25 ++++++++++++++++++++++--- docs/misc/xl-psr.markdown | 18 ++++++++++++------ 2 files changed, 34 insertions(+), 9 deletions(-) diff --git a/docs/man/xl.pod.1.in b/docs/man/xl.pod.1.in index 7caed08..5e7676e 100644 --- a/docs/man/xl.pod.1.in +++ b/docs/man/xl.pod.1.in @@ -1711,6 +1711,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] @@ -1735,7 +1738,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. @@ -1745,7 +1748,7 @@ 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 @@ -1762,6 +1765,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. @@ -1772,10 +1780,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