From: Ingo Molnar <mingo@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Borislav Petkov <bp@alien8.de>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [GIT PULL, v2] x86/microcode tree changes for v3.19
Date: Thu, 11 Dec 2014 07:25:08 +0100 [thread overview]
Message-ID: <20141211062508.GB5059@gmail.com> (raw)
In-Reply-To: <CA+55aFwiu2D=hKNvCvn-LL+TpYn9RS-N7+E8w7p+xLNdWSk8sA@mail.gmail.com>
* Linus Torvalds <torvalds@linux-foundation.org> wrote:
> On Wed, Dec 10, 2014 at 4:42 AM, Ingo Molnar <mingo@kernel.org> wrote:
> >
> > Please pull the latest x86-microcode-for-linus git tree from:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-microcode-for-linus
>
> Hmm. There's a conflict with commit 02ecc41abcea ("x86,
> microcode: Limit the microcode reloading to 64-bit for now"),
Sorry, should have mentioned that explicitly, but forgot about
it.
> but I'm going to assume that the issue is fixed now, and that
> commit fbae4ba8c4a3 ("x86, microcode: Reload microcode on
> resume") that causes the conflict also handles the 32-bit case
> correctly. So my merge is going to just remove the X86_64 test,
> effectively undoing that first commit, ratehr than keep it
> around.
>
> If it turns out that the 64-bit limitation needs to be still in
> place, holler. We can re-do the ugly 64-bit limit thing if
> required.
Hm, so in my own conflict resolution I kept that check, last I
heard Boris was still seeing weirdnesses (read: crashes) on
32-bit and I'm not sure even the full series fixes it all.
In any case, would be nice to double check this and reinstate the
limitation explicitly if it's still needed, or apply a fix.
Boris?
Thanks,
Ingo
next prev parent reply other threads:[~2014-12-11 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-09 13:27 [GIT PULL] x86/microcode tree changes for v3.19 Ingo Molnar
2014-12-10 12:42 ` [GIT PULL, v2] " Ingo Molnar
2014-12-11 5:25 ` Linus Torvalds
2014-12-11 6:25 ` Ingo Molnar [this message]
2014-12-11 9:12 ` Borislav Petkov
2014-12-11 12:25 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141211062508.GB5059@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.