From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <JBeulich@suse.com>,
xen-devel <xen-devel@lists.xenproject.org>
Cc: Keir Fraser <keir@xen.org>
Subject: Re: [PATCH] x86/AMD-ucode: correct multiple container handling
Date: Mon, 15 Dec 2014 09:57:16 -0600 [thread overview]
Message-ID: <548F04DC.3060306@amd.com> (raw)
In-Reply-To: <548EC61B.6000806@citrix.com>
On 12/15/2014 5:29 AM, Andrew Cooper wrote:
> On 15/12/14 09:16, Jan Beulich wrote:
>> Avoid emitting an error message referring to an incorrect or corrupt
>> container file just because no entry was found for the running CPU.
>>
>> Additionally switch the order of data validation and consumption in
>> cpu_request_microcode()'s first loop, and also check the types of
>> skipped blocks in container_fast_forward().
>>
>> Signed-off-by: Jan Beulich<jbeulich@suse.com>
>
> Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>
>
>
Reviewed-by: Aravind Gopalakrishnan <Aravind.Gopalakrishnan@amd.com>
prev parent reply other threads:[~2014-12-15 15:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 9:16 [PATCH] x86/AMD-ucode: correct multiple container handling Jan Beulich
2014-12-15 11:29 ` Andrew Cooper
2014-12-15 15:57 ` 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=548F04DC.3060306@amd.com \
--to=aravind.gopalakrishnan@amd.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=keir@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 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.