From mboxrd@z Thu Jan  1 00:00:00 1970
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
Subject: Re: [PATCH V3] docs,
	amd_ucode: Add AMD container file format notes
Date: Tue, 7 Oct 2014 09:41:33 -0500
Message-ID: <5433FB9D.7090805@amd.com>
References: <1412621867-4067-1-git-send-email-aravind.gopalakrishnan@amd.com>
	<5433EF4A.5090901@oracle.com> <1412689770.4972.30.camel@citrix.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
In-Reply-To: <1412689770.4972.30.camel@citrix.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: Ian Campbell <Ian.Campbell@citrix.com>, Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: andrew.cooper3@citrix.com, keir@xen.org, ian.jackson@eu.citrix.com, jbeulich@suse.com, xen-devel@lists.xen.org
List-Id: xen-devel@lists.xenproject.org

On 10/7/2014 8:49 AM, Ian Campbell wrote:
> On Tue, 2014-10-07 at 09:48 -0400, Boris Ostrovsky wrote:
>> 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.

Ok. There's one other instance where I will update this.
I shall leave the instances that are used for exemplification purposes 
untouched.

>> 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?
> It's completely fine to send patches against staging if the baseline you
> need is in there...
>
>

Ok, I shall base V3 patch off staging and send it as a separate patch.

Thanks,
-Aravind.