From: Jacob Shin <jacob.shin@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
Andreas Herrmann <herrmann.der.user@googlemail.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>, <x86@kernel.org>,
Fenghua Yu <fenghua.yu@intel.com>, Joe Perches <joe@perches.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH V3 4/4] microcode/x86/amd: early microcode patch loading support for AMD
Date: Thu, 6 Jun 2013 15:06:03 -0500 [thread overview]
Message-ID: <20130606200603.GA6952@jshin-Toonie> (raw)
In-Reply-To: <20130605221042.GE29856@pd.tnic>
On Thu, Jun 06, 2013 at 12:10:42AM +0200, Borislav Petkov wrote:
> On Fri, May 31, 2013 at 08:15:12PM -0500, Jacob Shin wrote:
> > Any thoughts on this Boris?
>
> Looks ok to me - I'm assuming you're testing all this new code on all
> families...?
Thanks, I have sent out a V2 of this patch. This time I remembered to
CC you on it :-) (sorry about V1)
Yes the new early load bits have been tested on variety of families,
and also 32 vs 64 bits, loading on cold boot vs suspend/resume, single
family container file vs multiple container files appended together,
.. etc.
prev parent reply other threads:[~2013-06-06 21:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-30 19:09 [PATCH V3 0/4] x86/microcode: early microcode patch loading support on AMD Jacob Shin
2013-05-30 19:09 ` [PATCH V3 1/4] x86, microcode, intel: Correct typo in printk Jacob Shin
2013-05-31 3:26 ` [tip:x86/microcode] " tip-bot for Borislav Petkov
2013-05-30 19:09 ` [PATCH V3 2/4] x86/microcode: vendor abstract out save_microcode_in_initrd() Jacob Shin
2013-05-31 3:27 ` [tip:x86/microcode] x86, microcode: Vendor " tip-bot for Jacob Shin
2013-05-30 19:09 ` [PATCH V3 3/4] x86/microcode/amd: refactor functions to prepare for early loading Jacob Shin
2013-05-31 3:29 ` [tip:x86/microcode] x86, microcode, amd: Refactor " tip-bot for Jacob Shin
2013-05-30 19:09 ` [PATCH V3 4/4] microcode/x86/amd: early microcode patch loading support for AMD Jacob Shin
2013-05-31 3:31 ` [tip:x86/microcode] x86, microcode, amd: Early " tip-bot for Jacob Shin
2013-05-31 6:10 ` Yinghai Lu
2013-05-31 6:59 ` Jacob Shin
2013-05-31 8:41 ` Borislav Petkov
2013-05-31 15:02 ` Jacob Shin
2013-05-31 15:13 ` H. Peter Anvin
2013-05-31 15:17 ` Jacob Shin
2013-05-31 21:59 ` [tip:x86/microcode] x86, microcode, amd: Fix warnings and errors on with CONFIG_MICROCODE=m tip-bot for Jacob Shin
2013-06-01 9:30 ` Borislav Petkov
2013-06-04 21:02 ` Yinghai Lu
2013-06-04 21:36 ` Jacob Shin
2013-06-04 21:55 ` Jacob Shin
2013-06-04 22:05 ` Yinghai Lu
2013-05-31 4:26 ` [PATCH V3 4/4] microcode/x86/amd: early microcode patch loading support for AMD Henrique de Moraes Holschuh
2013-05-31 15:54 ` Jacob Shin
2013-05-31 19:32 ` Andreas Herrmann
2013-05-31 21:30 ` Henrique de Moraes Holschuh
2013-06-01 1:15 ` Jacob Shin
2013-06-05 22:10 ` Borislav Petkov
2013-06-06 20:06 ` Jacob Shin [this message]
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=20130606200603.GA6952@jshin-Toonie \
--to=jacob.shin@amd.com \
--cc=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=herrmann.der.user@googlemail.com \
--cc=hmh@hmh.eng.br \
--cc=hpa@zytor.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox