From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754459Ab1JLWeQ (ORCPT ); Wed, 12 Oct 2011 18:34:16 -0400 Received: from claw.goop.org ([74.207.240.146]:46853 "EHLO claw.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753053Ab1JLWeP (ORCPT ); Wed, 12 Oct 2011 18:34:15 -0400 Message-ID: <4E9615E5.9050208@goop.org> Date: Wed, 12 Oct 2011 15:34:13 -0700 From: Jeremy Fitzhardinge User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0.1) Gecko/20110930 Thunderbird/7.0.1 MIME-Version: 1.0 To: "H. Peter Anvin" CC: Borislav Petkov , 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> <4E95F711.2090004@zytor.com> In-Reply-To: <4E95F711.2090004@zytor.com> X-Enigmail-Version: 1.3.2 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 10/12/2011 01:22 PM, H. Peter Anvin wrote: > On 10/12/2011 12:18 PM, Jeremy Fitzhardinge wrote: >> If there were a general shift to "this is how we're going to do >> microcode in the future", then Xen will happily go along for the ride. > > It *is* how we want to do microcode in the future. There is a > prototype for the Intel hardware side here; we just haven't had time > to finalize it partly because I got pulled onto the kernel.org situation. OK, great! Has there been any public discussion about this? J