[<prev] [next>] [day] [month] [year] [list]
Message-ID: <20134.59800.835498.929876@mariner.uk.xensource.com>
Date: Tue, 25 Oct 2011 17:53:44 +0100
From: Ian Jackson <Ian.Jackson@...citrix.com>
To: Borislav Petkov <bp@...64.org>
CC: Christoph Egger <Christoph.Egger@....com>,
Jeremy Fitzhardinge <jeremy@...p.org>,
Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
the arch/x86 maintainers <x86@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Xen Devel <xen-devel@...ts.xensource.com>,
Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
"H. Peter Anvin" <hpa@...or.com>, Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode
update in Xen dom0
Borislav Petkov writes ("Re: [Xen-devel] Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0"):
> No, you don't want to keep the existing API and you know it. I've
> explained to you last week why.
So should I submit a patchset to remove the existing post-boot
microcode loading from Linux ?
Ian.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists