From: Chao Peng <chao.p.peng@linux.intel.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: keir@xen.org, Ian.Campbell@citrix.com,
stefano.stabellini@eu.citrix.com, George.Dunlap@eu.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: Cache Allocation Technology(CAT) design for XEN
Date: Mon, 15 Dec 2014 16:47:51 +0800 [thread overview]
Message-ID: <20141215084751.GA3105@pengc-linux.bj.intel.com> (raw)
In-Reply-To: <548B0389.5040107@citrix.com>
On Fri, Dec 12, 2014 at 03:02:33PM +0000, Andrew Cooper wrote:
> On 12/12/14 12:27, Chao Peng wrote:
> > Hi all, we plan to bring Intel CAT into XEN. This is the initial
> > design for that. Comments/suggestions are welcome.
> >
>
> Fantastic - this is a very clear and well presented document. In terms
> of a plan of action, it looks fine.
Thank you for review.
>
> >From my understanding, CAT is a largely orthogonal to CMT, but will
> share some of the base PSR infrastructure in Xen?
>
Yes, from functional perspective, they are independent features. But
they do share some common codes and also have similar designs in XEN.
Chao
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-12-15 8:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 12:27 Cache Allocation Technology(CAT) design for XEN Chao Peng
2014-12-12 15:02 ` Andrew Cooper
2014-12-15 8:47 ` Chao Peng [this message]
2014-12-16 8:55 ` Chao Peng
2014-12-16 9:38 ` Jan Beulich
2014-12-17 11:07 ` Chao Peng
2014-12-18 17:54 ` Auld, Will
2014-12-18 16:40 ` Tim Deegan
2014-12-19 6:09 ` Chao Peng
2014-12-19 9:43 ` Tim Deegan
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=20141215084751.GA3105@pengc-linux.bj.intel.com \
--to=chao.p.peng@linux.intel.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.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.