xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Xen-devel List <xen-devel@lists.xen.org>,
	Jan Beulich <JBeulich@suse.com>,
	Kevin Tian <kevin.tian@intel.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	"Lai, Paul C" <paul.c.lai@intel.com>
Subject: PC8 Residency on Broadwell hardware
Date: Mon, 12 Sep 2016 09:47:59 +0100	[thread overview]
Message-ID: <2515b770-ee65-8d8c-6ddb-cfca01e087ba@citrix.com> (raw)

Hello,

c/s 350bc1a9d4 "x86: support newer Intel CPU models" changed the set of
MSRs read by Xeon Broadwell hardware (specifically, model 79 / 0x47).

Rereading the manual, it does indeed indicate that this MSR is available.

However, experimentally it is not.  All Broadwell hardware XenServer has
(both SDPs and production systems) reliably take a #GP fault when trying
to read this MSR.  Haswell hardware appears fine (and indeed, was
reading that MSR before).

Intel: Please can you confirm whether the documentation is correct?  If
it is, do you have any idea why the MSR might not be available?  I can't
spot anything relevant in the platform errata documents.

Thanks,

~Andrew

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

             reply	other threads:[~2016-09-12  8:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-12  8:47 Andrew Cooper [this message]
2016-09-12  9:00 ` PC8 Residency on Broadwell hardware Jan Beulich
2016-09-12 17:28   ` Nakajima, Jun
2016-09-13  7:51     ` Jan Beulich
2016-09-13  9:05       ` Andrew Cooper
2016-09-13 16:10         ` Nakajima, Jun
2016-09-18 23:24           ` Nakajima, Jun

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=2515b770-ee65-8d8c-6ddb-cfca01e087ba@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=paul.c.lai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).