Currently if a user tries to live-load the same or older ucode revision
than CPU already has, he will get a single message in Xen log like:
(XEN) 128 cores are to update their microcode
No actual ucode loading will happen and this situation can be quite
confusing. Fix this by starting ucode update only when the provided
ucode revision is higher than the currently cached one (if any).
This is based on the property that if microcode_cache exists, all CPUs
in the system should have at least that ucode revision.
Additionally, print a user friendly message if no matching or newer
ucode can be found in the provided blob. This also requires ignoring
-ENODATA in AMD-side code, otherwise the message given to the user is:
(XEN) Parsing microcode blob error -61
Which actually means that a ucode blob was parsed fine, but no matching
ucode was found.
Signed-off-by: Sergey Dyasli <sergey.dyasli@citrix.com>
Reviewed-by: Chao Gao <chao.gao@intel.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
Release-acked-by: Juergen Gross <jgross@suse.com>
if ( !patch )
{
+ printk(XENLOG_WARNING "microcode: couldn't find any matching ucode in "
+ "the provided blob!\n");
ret = -ENOENT;
goto put;
}
+ /*
+ * If microcode_cache exists, all CPUs in the system should have at least
+ * that ucode revision.
+ */
+ spin_lock(µcode_mutex);
+ if ( microcode_cache &&
+ microcode_ops->compare_patch(patch, microcode_cache) != NEW_UCODE )
+ {
+ spin_unlock(µcode_mutex);
+ printk(XENLOG_WARNING "microcode: couldn't find any newer revision "
+ "in the provided blob!\n");
+ microcode_free_patch(patch);
+ ret = -ENOENT;
+
+ goto put;
+ }
+ spin_unlock(µcode_mutex);
+
if ( microcode_ops->start_update )
{
ret = microcode_ops->start_update();
if ( error )
{
+ /*
+ * -ENODATA here means that the blob was parsed fine but no matching
+ * ucode was found. Don't return it to the caller.
+ */
+ if ( error == -ENODATA )
+ error = 0;
+
xfree(mc_amd->equiv_cpu_table);
xfree(mc_amd);
goto out;