lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 12 Oct 2011 17:03:50 -0700 From: "H. Peter Anvin" <hpa@...or.com> To: Jeremy Fitzhardinge <jeremy@...p.org> CC: Borislav Petkov <bp@...64.org>, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>, the arch/x86 maintainers <x86@...nel.org>, Tigran Aivazian <tigran@...azian.fsnet.co.uk>, Xen Devel <xen-devel@...ts.xensource.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Jeremy Fitzhardinge <jeremy.fitzhardinge@...rix.com>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [PATCH 0/3] x86/microcode: support for microcode update in Xen dom0 On 10/12/2011 05:00 PM, Jeremy Fitzhardinge wrote: > > Presumably we'd want some way to make all possible microcode files > available to the hypervisor/kernel so that there's no need to construct > the bootloader config for a specific CPU vendor (or worse, CPU model). > So that would need either some way of specifying multiple files, or a > wrapper which can contain multiple files? > I have been thinking a "bundle" format with a per-vendor header followed by the microcode in the appropriate format for each vendor. -hpa -- 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