From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: keir@xen.org,
Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH V3] x86, amd_ucode: Support multiple container files appended together
Date: Fri, 27 Jun 2014 08:47:55 -0400 [thread overview]
Message-ID: <53AD67FB.80409@oracle.com> (raw)
In-Reply-To: <53AD4458020000780001DDAA@mail.emea.novell.com>
On 06/27/2014 04:15 AM, Jan Beulich wrote:
>>>> On 26.06.14 at 22:00, <boris.ostrovsky@oracle.com> wrote:
>> The trouble is that if I have two files in my hands, both called
>> microcode_amd_fam15h.bin, I don't know which one is the more up-to-date
>> (would be nice to have a tool to print file info).
>>
>> Of course, one can argue that in that case I shouldn't be using neither
>> but HW makes its own verification of patches so in principle trying both
>> should be safe (provided that SW tries not to load older revision).
> I think we should focus on getting things to work with realistic
> blobs, i.e. such that distros and their tools would generate. If you
> update a respective package, it'll be clear which blob is the latest,
> and there's generally not going to be two blobs for the same family
> put on a single system. People obtaining ucode blobs manually from
> elsewhere should know what they're doing and not try to paste
> together two of them targeting the same family.
Ok.
I only mention this scenario because I myself needed to deal with this
(on more than one occasion, in fact) when I had two containers and
didn't know which one is which.
-boris
next prev parent reply other threads:[~2014-06-27 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-26 16:01 [PATCH V3] x86, amd_ucode: Support multiple container files appended together Boris Ostrovsky
2014-06-26 16:37 ` Aravind Gopalakrishnan
2014-06-26 20:00 ` Boris Ostrovsky
2014-06-26 21:55 ` Aravind Gopalakrishnan
2014-06-27 2:04 ` Boris Ostrovsky
2014-06-27 8:15 ` Jan Beulich
2014-06-27 12:47 ` Boris Ostrovsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-25 19:34 Aravind Gopalakrishnan
2014-06-26 13:14 ` Boris Ostrovsky
2014-06-26 15:03 ` Aravind Gopalakrishnan
2014-06-27 10:50 ` Jan Beulich
2014-06-27 17:07 ` Aravind Gopalakrishnan
2014-06-30 9:32 ` Jan Beulich
2014-06-30 16:51 ` Aravind Gopalakrishnan
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=53AD67FB.80409@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=JBeulich@suse.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=keir@xen.org \
--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.