All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Ross Lagerwall <ross.lagerwall@citrix.com>,
	Tim Deegan <tim@xen.org>
Cc: Kevin Tian <kevin.tian@intel.com>, Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Eddie Dong <eddie.dong@intel.com>,
	xen-devel@lists.xen.org, Jun Nakajima <jun.nakajima@intel.com>,
	Keir Fraser <keir@xen.org>
Subject: Re: [PATCHv2 for-4.6] p2m/ept: Work around hardware errata setting A bit
Date: Mon, 28 Sep 2015 15:48:24 +0100	[thread overview]
Message-ID: <56095338.9040504@citrix.com> (raw)
In-Reply-To: <560964B402000078000A6367@prv-mh.provo.novell.com>

On 28/09/15 15:03, Jan Beulich wrote:
>>>> On 28.09.15 at 14:43, <tim@xen.org> wrote:
>> At 13:39 +0100 on 28 Sep (1443447574), Ross Lagerwall wrote:
>>> @@ -1150,6 +1152,9 @@ int ept_p2m_init(struct p2m_domain *p2m)
>>>      p2m->memory_type_changed = ept_memory_type_changed;
>>>      p2m->audit_p2m = NULL;
>>>  
>>> +    /* Work around Errata AVR41 on Avaton processors. */
>>> +    cpu_has_ept_ad = boot_cpu_data.x86_model != 0x4d;
>>> +
>> Shouldn't this check the family (a.k.a. boot_cpu_data.x86) too?
> Definitely. Considering that the spec update says that the firmware
> may contain a workaround (microcode update) perhaps even the
> stepping and microcode level would need looking at.

There are no details available as to what firmware fix might be
available, nor how to determine whether the issue is fixed.

~Andrew

  reply	other threads:[~2015-09-28 14:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-28 12:39 [PATCHv2 for-4.6] p2m/ept: Work around hardware errata setting A bit Ross Lagerwall
2015-09-28 12:43 ` Tim Deegan
2015-09-28 14:03   ` Jan Beulich
2015-09-28 14:48     ` Andrew Cooper [this message]
2015-09-28 14:51       ` Jan Beulich
2015-09-28 12:43 ` Wei Liu
2015-09-28 14:09 ` Jan Beulich
2015-09-28 16:50   ` George Dunlap
2015-09-30  9:17   ` Kai Huang
2015-09-30  9:21 ` Wei Liu

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=56095338.9040504@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=eddie.dong@intel.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=keir@xen.org \
    --cc=kevin.tian@intel.com \
    --cc=ross.lagerwall@citrix.com \
    --cc=tim@xen.org \
    --cc=wei.liu2@citrix.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.