From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754517Ab1JLWuU (ORCPT ); Wed, 12 Oct 2011 18:50:20 -0400 Received: from terminus.zytor.com ([198.137.202.10]:34562 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752188Ab1JLWuS (ORCPT ); Wed, 12 Oct 2011 18:50:18 -0400 Message-ID: <4E96198F.4030906@zytor.com> Date: Wed, 12 Oct 2011 15:49:51 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: Borislav Petkov CC: Konrad Rzeszutek Wilk , Jeremy Fitzhardinge , the arch/x86 maintainers , Tigran Aivazian , Xen Devel , Linux Kernel Mailing List , Jeremy Fitzhardinge , Ingo Molnar , Thomas Gleixner Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 References: <4E94E1E5.4070505@goop.org> <20111012101615.GA14966@aftab> <4E95D9E7.6090304@zytor.com> <4E95E7FE.6050302@goop.org> <20111012194543.GD14966@aftab> <20111012204048.GA22260@phenom.oracle.com> <4E960746.90805@zytor.com> <20111012214013.GD28723@aftab> In-Reply-To: <20111012214013.GD28723@aftab> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The stickiest part of all of this is where to leave the microcode so the kernel can get to it way early. We could use the linked list, but that would mean bootloader enabling; another idea was to stick it as a prefix to the initramfs identified by a signature. -hpa