From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>, jbeulich@suse.com
Cc: boris.ostrovsky@oracle.com, xen-devel@lists.xen.org,
keir@xen.org, Suravee.Suthikulpanit@amd.com, "Hurwitz,
Sherry" <sherry.hurwitz@amd.com>
Subject: Re: [PATCH] x86, amd_ucode: Skip microcode updates for final levels
Date: Fri, 31 Jul 2015 15:51:24 -0500 [thread overview]
Message-ID: <55BBDFCC.8000401@amd.com> (raw)
In-Reply-To: <55BBDF1C.3080809@citrix.com>
On 7/31/2015 3:48 PM, Andrew Cooper wrote:
>
>> So, the patch id values have only been obtained empirically.
>> The Linux patch provides the bug reference for
>> this:https://bugzilla.suse.com/show_bug.cgi?id=913996
>> (It's a fairly long thread but the gist of it is that people
>> predominantly seem to be experiencing system hang issues
>> when they try to update microcode levels from these patch ids:
>> 0x01000098, 0x0100009f, 0x010000af)
>>
>> From discussing about it internally, we gathered that OS/hypervisor
>> cannot reliably perform microcode updates beyond these specified levels
>> due to HW issues.
> Ok - please include this information in the comment as well please.
>
Will do that.
Thanks,
-Aravind.
prev parent reply other threads:[~2015-07-31 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-30 16:23 [PATCH] x86, amd_ucode: Skip microcode updates for final levels Aravind Gopalakrishnan
2015-07-30 16:41 ` Boris Ostrovsky
2015-07-30 17:01 ` Andrew Cooper
2015-07-31 20:45 ` Aravind Gopalakrishnan
2015-07-31 20:48 ` Andrew Cooper
2015-07-31 20:51 ` Aravind Gopalakrishnan [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=55BBDFCC.8000401@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=keir@xen.org \
--cc=sherry.hurwitz@amd.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.