From: Jan Beulich <jbeulich@suse.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
"Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [Xen-devel] [PATCH 2/4] x86/ucode: Fix error paths in apply_microcode()
Date: Mon, 23 Mar 2020 09:32:39 +0100 [thread overview]
Message-ID: <beef054b-17de-ada1-badb-df4ff9c5b16e@suse.com> (raw)
In-Reply-To: <20200320212453.21685-3-andrew.cooper3@citrix.com>
On 20.03.2020 22:24, Andrew Cooper wrote:
> @@ -259,15 +260,14 @@ static int apply_microcode(const struct microcode_patch *patch)
> /* check current patch id and patch's id for match */
> if ( hw_err || (rev != hdr->patch_id) )
> {
> - printk(KERN_ERR "microcode: CPU%d update from revision "
> - "%#x to %#x failed\n", cpu, rev, hdr->patch_id);
> + printk(XENLOG_ERR
> + "microcode: CPU%u update rev %#x to %#x failed, result %#x\n",
> + cpu, old_rev, hdr->patch_id, rev);
> return -EIO;
> }
>
> - printk(KERN_WARNING "microcode: CPU%d updated from revision %#x to %#x\n",
> - cpu, sig->rev, hdr->patch_id);
> -
> - sig->rev = rev;
> + printk(XENLOG_WARNING "microcode: CPU%u updated from revision %#x to %#x\n",
> + cpu, old_rev, hdr->patch_id);
Prefer the local variable here over hdr->patch_id, just like you do
on the Intel side?
Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2020-03-23 8:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-20 21:24 [Xen-devel] [PATCH 0/4] x86/ucode: Cleanup - Part 2/n Andrew Cooper
2020-03-20 21:24 ` [Xen-devel] [PATCH 1/4] x86/ucode/amd: Fix assertion in compare_patch() Andrew Cooper
2020-03-21 16:45 ` Wei Liu
2020-03-20 21:24 ` [Xen-devel] [PATCH 2/4] x86/ucode: Fix error paths in apply_microcode() Andrew Cooper
2020-03-21 16:49 ` Wei Liu
2020-03-23 8:32 ` Jan Beulich [this message]
2020-03-20 21:24 ` [Xen-devel] [PATCH 3/4] xen: Drop raw_smp_processor_id() Andrew Cooper
2020-03-21 10:14 ` Julien Grall
2020-03-21 16:50 ` Wei Liu
2020-03-20 21:24 ` [Xen-devel] [PATCH 4/4] xen: Introduce a xmemdup_bytes() helper Andrew Cooper
2020-03-21 16:51 ` Wei Liu
2020-03-21 22:19 ` Julien Grall
2020-03-23 8:38 ` Jan Beulich
2020-03-26 15:38 ` Andrew Cooper
2020-03-26 15:47 ` Jan Beulich
2020-03-26 14:53 ` Andrew Cooper
2020-03-26 19:05 ` Julien Grall
2020-03-23 8:41 ` [Xen-devel] [PATCH 0/4] x86/ucode: Cleanup - Part 2/n 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=beef054b-17de-ada1-badb-df4ff9c5b16e@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.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).