From: "Jan Beulich" <jbeulich@suse.com>
To: xumengpanda@gmail.com, chao.p.peng@linux.intel.com
Cc: andrew.cooper3@citrix.com, xen-devel@lists.xen.org,
priya.v.autee@intel.com
Subject: Re: Question about the CAT and CMT in Xen
Date: Wed, 02 Sep 2015 02:34:00 -0600 [thread overview]
Message-ID: <55E6C28802000078000D7CC0@prv-mh.provo.novell.com> (raw)
In-Reply-To: <CAENZ-+kxByV7rzQs_QRFS-dhpUvS=iPPTuZLLbexz4N5W-7U0A@mail.gmail.com>
>>> Meng Xu <xumengpanda@gmail.com> 09/02/15 4:57 AM >>>
>2015-09-01 22:31 GMT-04:00 Chao Peng <chao.p.peng@linux.intel.com>:
>> On Tue, Sep 01, 2015 at 09:51:57PM -0400, Meng Xu wrote:
>>> Hi Andrew and Chao,
>>>
>>> [Important things go first] It turns out my machine (Intel E5-2618L
>>> v3) does have CAT capability!
>>> Xen gives the false alarm that my machine does not have it. This
>>> should be a bug, IMO. :-)
>>
>> Even some Haswell Servers do support CAT, but it's usually
>> model-specific and the feature is not enumerated in a standard way as
>> listed in Intel SDM. Xen now however only takes care of the standard
>> enumeration so your case is not detected.
>
>Ah. I prefer not to upgrade the firmware... Last time when I upgrade
>the firmware, I screw up the whole system. :-(
I would very much expect this to be an exception, not the norm.
>Is it possible to check if CAT is supported on a machine with another
>way? Right now, I think you are checking some specific bits returned
>by CPUID.
That's the one and only way it should be done in production software.
For your own debugging/development purposes you could of course
extend that check.
Jan
prev parent reply other threads:[~2015-09-02 8:34 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
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 [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=55E6C28802000078000D7CC0@prv-mh.provo.novell.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=chao.p.peng@linux.intel.com \
--cc=priya.v.autee@intel.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.