From: Igor Druzhinin <igor.druzhinin@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: <xen-devel@lists.xenproject.org>, <andrew.cooper3@citrix.com>,
<roger.pau@citrix.com>, <wl@xen.org>, <jun.nakajima@intel.com>,
<kevin.tian@intel.com>
Subject: Re: [PATCH 1/2] x86/intel: insert Ice Lake X (server) model numbers
Date: Wed, 14 Oct 2020 17:42:13 +0100 [thread overview]
Message-ID: <e30f7f98-ee1a-1a24-0496-01911a79c861@citrix.com> (raw)
In-Reply-To: <ca9a1cce-1e51-0f55-4527-42f48bc7d6ab@suse.com>
On 14/10/2020 16:47, Jan Beulich wrote:
> On 13.10.2020 05:02, Igor Druzhinin wrote:
>> LBR, C-state MSRs and if_pschange_mc erratum applicability should correspond
>> to Ice Lake desktop according to External Design Specification vol.2.
>
> Could you tell me where this is publicly available? Even after spending
> quite a bit of time on searching for it, I can't seem to be able to
> find it. And the SDM doesn't have enough information (yet).
True that SDM doesn't have this data. As I mentioned that data is taken from
External Design Specification for Ice Lake server which is accessed using Intel
account. I'm not completely sure it is right to make changes in open source
project like Linux or Xen based on information which is not publicly available
yet. But Intel is frequently doing this with Linux : even my second patch uses
data taken from one of these documents and was committed by Intel to Linux first.
Do we need the information publicly available to commit these changes as well?
If not, we can run with these changes in our patchqueue until it gets out properly.
Igor
next prev parent reply other threads:[~2020-10-14 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-13 3:02 [PATCH 1/2] x86/intel: insert Ice Lake X (server) model numbers Igor Druzhinin
2020-10-13 3:02 ` [PATCH 2/2] x86/mwait-idle: Customize IceLake server support Igor Druzhinin
2020-10-14 16:09 ` Jan Beulich
2020-10-14 15:47 ` [PATCH 1/2] x86/intel: insert Ice Lake X (server) model numbers Jan Beulich
2020-10-14 16:42 ` Igor Druzhinin [this message]
2020-10-15 7:11 ` 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=e30f7f98-ee1a-1a24-0496-01911a79c861@citrix.com \
--to=igor.druzhinin@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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).