All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Borislav Petkov <bp@alien8.de>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/microcode: Adjust ramdisk address when accessing by virtual address
Date: Mon, 19 Dec 2016 13:12:25 -0500	[thread overview]
Message-ID: <f9a50117-b404-da6f-e54a-f8b40e765c1b@oracle.com> (raw)
In-Reply-To: <20161219180709.2tsvsebagdiyxxrs@pd.tnic>

On 12/19/2016 01:07 PM, Borislav Petkov wrote:
> On Mon, Dec 19, 2016 at 05:40:27PM +0100, Borislav Petkov wrote:
>> On Mon, Dec 19, 2016 at 11:10:29AM -0500, Boris Ostrovsky wrote:
>>> config attached. I'll see how I can get you the initrd.
>> Wait a bit, lemme see if I can repro with my initrd here.
> Hmm, it boots here (btw, this is with the 4 patches applied).
>
> [    0.000000] Linux version 4.9.0upstream-11409-gf3302378ed83-dirty (boris@pd) (gcc version 6.2.1 20161124 (Debian 6.2.1-5) ) #1 SMP Mon Dec 19 18:50:17 CET 2016
> [    0.000000] x86/fpu: Legacy x87 FPU detected.
> [    0.000000] e820: BIOS-provided physical RAM map:
> ...
> [    0.000000] RAMDISK: [mem 0x37845000-0x37c19fff]
> [    0.000000] Allocated new RAMDISK: [mem 0x36470000-0x36844f5e]
> [    0.000000] Move RAMDISK from [mem 0x37845000-0x37c19f5e] to [mem 0x36470000-0x36844f5e]
> ...
> [    0.243326] smpboot: CPU0: AMD E-350 Processor (family: 0x14, model: 0x1, stepping: 0x0)

IIUIC find_microcode_in_initrd() is called with paging on only on Intel
(which is where I observed it).


> [    0.243637] Performance Events: AMD PMU driver.
> ...
> [    1.307957] microcode: microcode updated early to new patch_level=0x05000029
> [    1.308212] microcode: CPU0: patch_level=0x05000029
> [    1.308374] microcode: CPU1: patch_level=0x05000029
> [    1.308726] microcode: Microcode Update Driver: v2.2.
>
> $ uname -a
> Linux x1 4.9.0upstream-11409-gf3302378ed83-dirty #1 SMP Mon Dec 19 18:50:17 CET 2016 i686 GNU/Linux
>
> So I guess I wanna take a look at the initrd now...


It'll have to wait until (my) evening, I'll ping you then.


-boris

  reply	other threads:[~2016-12-19 18:12 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-19 15:32 [PATCH] x86/microcode: Adjust ramdisk address when accessing by virtual address Boris Ostrovsky
2016-12-19 15:37 ` Borislav Petkov
2016-12-19 16:10   ` Boris Ostrovsky
2016-12-19 16:40     ` Borislav Petkov
2016-12-19 18:07       ` Borislav Petkov
2016-12-19 18:12         ` Boris Ostrovsky [this message]
2016-12-19 18:43           ` Borislav Petkov
2016-12-19 23:32             ` Borislav Petkov
2016-12-20  1:27               ` Boris Ostrovsky
2016-12-20  1:40                 ` Boris Ostrovsky
2016-12-20 14:40                   ` Borislav Petkov
2016-12-20 19:26                     ` Boris Ostrovsky
2016-12-20 19:31                       ` Borislav Petkov
2016-12-20 22:48                         ` Boris Ostrovsky
2016-12-20 22:55                           ` Borislav Petkov
2016-12-21  9:55                     ` [tip:x86/urgent] x86/microcode/AMD: Reload proper initrd start address tip-bot for Borislav Petkov

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=f9a50117-b404-da6f-e54a-f8b40e765c1b@oracle.com \
    --to=boris.ostrovsky@oracle.com \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.