From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>,
ian.campbell@citrix.com, jbeulich@suse.com,
andrew.cooper3@citrix.com, xen-devel@lists.xen.org
Cc: keir@xen.org, ian.jackson@eu.citrix.com
Subject: Re: [PATCH V3] docs, amd_ucode: Add AMD container file format notes
Date: Tue, 07 Oct 2014 09:48:58 -0400 [thread overview]
Message-ID: <5433EF4A.5090901@oracle.com> (raw)
In-Reply-To: <1412621867-4067-1-git-send-email-aravind.gopalakrishnan@amd.com>
On 10/06/2014 02:57 PM, Aravind Gopalakrishnan wrote:
> +-------------------------------------------------
> +
> +Intro to AMD Container Files:
> +-----------------------------
> +
> +* Beginning with processor family 10h, AMD provides microcode patch support.
> +* There is one single file (container file) containing all microcode patches
> + for AMD families 10h - 14h processors. [microcode_amd.bin]
> +* For AMD family 15h processors there is a separate container file. [microcode_amd_fam15h.bin]
I think this would need to be updated to 15h+ as well (i.e. new file
name for all 15h and later processors). Here and in a couple of places
below.
Since it's apparently already in the staging tree perhaps you can wait
until it shows up in the mainline and then send a patch?
-boris
next prev parent reply other threads:[~2014-10-07 13:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-06 18:57 [PATCH V3] docs, amd_ucode: Add AMD container file format notes Aravind Gopalakrishnan
2014-10-07 8:31 ` Ian Campbell
2014-10-07 13:48 ` Boris Ostrovsky [this message]
2014-10-07 13:49 ` Ian Campbell
2014-10-07 14:41 ` 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=5433EF4A.5090901@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=andrew.cooper3@citrix.com \
--cc=aravind.gopalakrishnan@amd.com \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.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.