[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130812153719.2b357d5d@fem.tu-ilmenau.de>
Date: Mon, 12 Aug 2013 15:37:19 +0200
From: Johannes Hirte <johannes.hirte@....tu-ilmenau.de>
To: Borislav Petkov <bp@...en8.de>
Cc: Torsten Kaiser <just.for.lkml@...glemail.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Jacob Shin <jacob.shin@....com>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] x86, AMD: simplify load_microcode_amd() to fix
early microcode loading to no longer access uninitialized per-cpu data
On Thu, 8 Aug 2013 21:29:43 +0200
Borislav Petkov <bp@...en8.de> wrote:
> On Wed, Jul 24, 2013 at 09:32:50PM +0200, Borislav Petkov wrote:
> > Btw, this patch is the one that fixes the boot issue on your box,
> > correct?
> >
> > If so, please put a minimal version of it in the next patch set
> > you're sending right after
>
> Ok, I've wiggled it ontop of the cpu_has_amd_erratum() patch, see
> below. Can you guys - Torsten and Johannes - run this branch here:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git amd-ucode
>
> to check whether you can boot your boxes with he failing configs? I
> mean, I tried reproducing with your configs on my F10h box and no
> luck - box boots just fine. And it is affected by E400 so...
>
> In any case, the two patches make sense regardless so if they fix your
> issues, I'd like to send them upwards soonish.
>
> Thanks.
Just tested your amd-ucode branch with CONFIG_MICROCODE_AMD_EARLY
re-enabled and it works so far.
--
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