From: "H. Peter Anvin" Subject: Re: [PATCH 0/2] x86/microcode: support for microcode update in Xen dom0 Date: Wed, 02 Feb 2011 16:58:10 -0800 Message-ID: <4D49FDA2.9020900@zytor.com> References: <20110130113356.GA27967@liondog.tnic> <4D461FB9.5050807@goop.org> <20110131070241.GA22071@liondog.tnic> <4D46FC9F.6090309@goop.org> <20110131234131.GA16095@liondog.tnic> <4D475099.1080004@goop.org> <4D475DB5.1020300@zytor.com> <4D488EB1.9020803@goop.org> <4D49B5F6.5010606@zytor.com> <4D49B903.2080602@goop.org> <20110203005517.GA30220@khazad-dum.debian.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110203005517.GA30220@khazad-dum.debian.net> Sender: linux-kernel-owner@vger.kernel.org To: Henrique de Moraes Holschuh Cc: Jeremy Fitzhardinge , Borislav Petkov , Ingo Molnar , the arch/x86 maintainers , Linux Kernel Mailing List , Xen Devel , Keir Fraser List-Id: xen-devel@lists.xenproject.org On 02/02/2011 04:55 PM, Henrique de Moraes Holschuh wrote: > > But I'd really, really appreciate if someone from Intel [that actually cares > for operating system support of microcode updates] could vouch that we're > allowed to do that (convert their text packs to binary packs, merge > microcodes from older packs with the new to have a single pack with all > microcodes in their most up-to-date revision, and distribute the resulting > binary packs) before I make the tool public. > I'm trying to figure this stuff out already. The actual conversion isn't a problem, obviously. -hpa