All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Chao Peng <chao.p.peng@linux.intel.com>
Cc: keir@xen.org, stefano.stabellini@eu.citrix.com,
	andrew.cooper3@citrix.com, Ian.Jackson@eu.citrix.com,
	xen-devel@lists.xen.org, will.auld@intel.com, JBeulich@suse.com,
	wei.liu2@citrix.com, dgdegra@tycho.nsa.gov
Subject: Re: [PATCH v5 13/13] docs: add xl-psr.markdown
Date: Tue, 21 Apr 2015 15:05:33 +0100	[thread overview]
Message-ID: <1429625133.4743.105.camel@citrix.com> (raw)
In-Reply-To: <1429281230-4352-14-git-send-email-chao.p.peng@linux.intel.com>

On Fri, 2015-04-17 at 22:33 +0800, Chao Peng wrote:
> @@ -1534,7 +1540,8 @@ Show CAT hardware information.
>  
>  =item B<psr-cat-cbm-set> [I<OPTIONS>] I<domain-id> I<cbm>
>  
> -Set cache capacity bitmasks(CBM) for a domain.
> +Set cache capacity bitmasks(CBM) for a domain. For how to specify I<cbm>
> +please refer to the link above.

I think the "link above" is to far. I think say something more explicit
like L<xl-psr.txt> ?

>  
>  B<OPTIONS>
>  
> @@ -1575,6 +1582,7 @@ And the following documents on the xen.org website:
>  L<http://xenbits.xen.org/docs/unstable/misc/xl-network-configuration.html>
>  L<http://xenbits.xen.org/docs/unstable/misc/xl-disk-configuration.txt>
>  L<http://xenbits.xen.org/docs/unstable/misc/xsm-flask.txt>
> +L<http://xenbits.xen.org/docs/unstable/misc/xl-psr.html>
>  
>  For systems that don't automatically bring CPU online:
>  
> diff --git a/docs/misc/xl-psr.markdown b/docs/misc/xl-psr.markdown
> new file mode 100644
> index 0000000..d167b84
> --- /dev/null
> +++ b/docs/misc/xl-psr.markdown
> @@ -0,0 +1,134 @@
> +# Intel Platform Shared Resource Monitoring/Control in xl
> +
> +This document introduces Intel Platform Shared Resource Monitoring/Control
> +technologies, their basic concepts and the xl interfaces.
> +
> +## Cache Monitoring Technology (CMT)
> +
> +Cache Monitoring Technology (CMT) is a new feature available on Intel Haswell
> +and later server platforms that allows an OS or Hypervisor/VMM to determine
> +the usage of cache(currently only L3 cache supported) by applications running
                     ^space before ( please.

> +For example, assuming a system with 8 portions and 3 domains:
> +
> +        A CBM of 0xff for every domain means each domain can access the
> +        whole cache. This is the default.
> +
> +        Giving one domain a CBM of 0x0f and the other two domain's 0xf0
> +        means that the first domain gets exclusive access to half of the
> +        cache (half of the portions) and the other two will share the
> +        other half.
> +
> +        Giving one domain a CBM of 0x0f, one 0x30 and the last 0xc0
> +        would give the first domain exclusive access to half the cache,
> +        and the other two exclusive access to one quarter each.

How does markdown render this? I think you might want to start each para
with a * to make it a bullet list.

Other than those minor things all looks good, thanks.

Ian.

      reply	other threads:[~2015-04-21 14:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-17 14:33 [PATCH v5 00/13] enable Cache Allocation Technology (CAT) for VMs Chao Peng
2015-04-17 14:33 ` [PATCH v5 01/13] x86: add socket_to_cpumask Chao Peng
2015-04-17 14:33 ` [PATCH v5 02/13] x86: improve psr scheduling code Chao Peng
2015-04-20 15:42   ` Dario Faggioli
2015-04-17 14:33 ` [PATCH v5 03/13] x86: detect and initialize Intel CAT feature Chao Peng
2015-04-20 16:13   ` Dario Faggioli
2015-04-21  9:39     ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 04/13] x86: maintain COS to CBM mapping for each socket Chao Peng
2015-04-17 14:33 ` [PATCH v5 05/13] x86: add COS information for each domain Chao Peng
2015-04-20 15:50   ` Andrew Cooper
2015-04-17 14:33 ` [PATCH v5 06/13] x86: expose CBM length and COS number information Chao Peng
2015-04-17 14:33 ` [PATCH v5 07/13] x86: dynamically get/set CBM for a domain Chao Peng
2015-04-20 15:52   ` Andrew Cooper
2015-04-21  9:42     ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 08/13] x86: add scheduling support for Intel CAT Chao Peng
2015-04-17 14:33 ` [PATCH v5 09/13] xsm: add CAT related xsm policies Chao Peng
2015-04-17 14:33 ` [PATCH v5 10/13] tools/libxl: minor name changes for CMT commands Chao Peng
2015-04-20 16:07   ` Dario Faggioli
2015-04-21 13:56     ` Ian Campbell
2015-04-17 14:33 ` [PATCH v5 11/13] tools/libxl: add command to show CMT hardware info Chao Peng
2015-04-21  0:37   ` Dario Faggioli
2015-04-21  9:42     ` Chao Peng
2015-04-21 13:57     ` Ian Campbell
2015-04-17 14:33 ` [PATCH v5 12/13] tools: add tools support for Intel CAT Chao Peng
2015-04-21  1:24   ` Dario Faggioli
2015-04-21  9:49     ` Chao Peng
2015-04-21 14:01       ` Ian Campbell
2015-04-21 14:39         ` Dario Faggioli
2015-04-22 13:09           ` Chao Peng
2015-04-21 15:15       ` Dario Faggioli
2015-04-22 13:37         ` Chao Peng
2015-04-17 14:33 ` [PATCH v5 13/13] docs: add xl-psr.markdown Chao Peng
2015-04-21 14:05   ` Ian Campbell [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1429625133.4743.105.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=wei.liu2@citrix.com \
    --cc=will.auld@intel.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.