[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120820201947.GC15006@aftab.osrc.amd.com>
Date: Mon, 20 Aug 2012 22:19:47 +0200
From: Borislav Petkov <bp@...64.org>
To: "H. Peter Anvin" <hpa@...or.com>
Cc: "Yu, Fenghua" <fenghua.yu@...el.com>,
Henrique de Moraes Holschuh <hmh@....eng.br>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
"Mallick, Asit K" <asit.k.mallick@...el.com>,
Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
Andreas Herrmann <andreas.herrmann3@....com>,
Borislav Petkov <borislav.petkov@....com>,
linux-kernel <linux-kernel@...r.kernel.org>, x86 <x86@...nel.org>
Subject: Re: [PATCH 04/11] x86/microcode_core_early.c: Define interfaces for
early load ucode
On Mon, Aug 20, 2012 at 01:08:49PM -0700, H. Peter Anvin wrote:
> On 08/20/2012 07:06 AM, Borislav Petkov wrote:
> >
> > Or,
> >
> > in case we want to supply more vendor-specific stuff early at boot, we
> > could do:
> >
> > kernel/x86/<vendor>/microcode...
> > |-> bios_overrides
> > |-> ...
> >
> > and have this layout extensible from the beginning...
> >
> Does that make sense, though?
Only time will tell. I was simply saying that we should leave ourselves
the door opened, should we need functionality like that in the future.
> I'm a bit concerned about having multiple files named microcode.bin by
> default; the pathname isn't as sticky as the filename when people move
> things around...
Ok, I see.
How about the following scheme then:
kernel/x86/<vendor>-microcode.bin
kernel/x86/<vendor>-bios-overrides.blob
...
?
All I'm saying is maybe we should impose some sanity rules now before
people go crazy with this and things get out of hands...
--
Regards/Gruss,
Boris.
Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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