All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Peng <chao.p.peng@linux.intel.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Question about the CAT and CMT in Xen
Date: Tue, 1 Sep 2015 13:47:16 +0800	[thread overview]
Message-ID: <20150901054716.GA19417@pengc-linux.bj.intel.com> (raw)
In-Reply-To: <CAENZ-+mO7D6tqOctYmzbYkeUAZQ2anhY8mxyw5PCRqKOuyYLwA@mail.gmail.com>

On Mon, Aug 31, 2015 at 04:09:31PM -0400, Meng Xu wrote:
> I looked into the xen/arch/x86/psr.c and found that the function
> cat_cpu_init() just returned without initializing the variable
> "cat_socket_enable".
> 
> Both  !cpu_has(c, X86_FEATURE_CAT) and c->cpuid_level <
> PSR_CPUID_LEVEL_CAT are evaluated as 1 inside the function
> cat_cpu_init().
> 
> OK. I understand that  the cpuid info shows that the CPU does not
> support CAT. However, according to the table at
> http://www.intel.com/content/www/us/en/communications/cache-monitoring-cache-allocation-technologies.html,
>  Intel(R) Xeon(R) CPU E5-2618L v3 should support CAT.
> 
> I'm not sure which part is incorrect: the hardware or the software?
> (Hope Chao could give some insight about this.)
> 

Hmmm, from cpuid info it looks like this model does not support CAT. I'm
not sure which microarchitecture it is. But if it is broadwell, hardware
should support that, what you need is some fireware update, just as Andrew
has said. But otherwise it is haswell, then the hardware probably doesn't
support that. In that case the above link probably is also wrong. I can check
that internally.

Chao

  parent reply	other threads:[~2015-09-01  5:47 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 17:42 Question about the CAT and CMT in Xen Meng Xu
2015-08-31 18:25 ` Andrew Cooper
2015-08-31 20:09   ` Meng Xu
2015-08-31 20:22     ` Andrew Cooper
2015-09-01  5:47     ` Chao Peng [this message]
2015-09-01 12:55       ` Meng Xu
2015-09-01 13:04         ` Andrew Cooper
2015-09-01 14:20           ` Meng Xu
2015-09-01 14:30             ` Andrew Cooper
2015-09-01 14:42               ` Meng Xu
2015-09-02  1:47                 ` Chao Peng
2015-09-02  1:53                   ` Meng Xu
2015-09-02  1:51                 ` Meng Xu
2015-09-02  2:31                   ` Chao Peng
2015-09-02  2:55                     ` Meng Xu
2015-09-02  8:34                       ` Jan Beulich

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=20150901054716.GA19417@pengc-linux.bj.intel.com \
    --to=chao.p.peng@linux.intel.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=xen-devel@lists.xen.org \
    --cc=xumengpanda@gmail.com \
    /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.