mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@gmail.com>
To: Borislav Petkov <bp@suse.de>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Builtin microcode does nothing..
Date: Sat, 21 May 2016 04:59:15 +0200	[thread overview]
Message-ID: <86dacf1e-83ca-8dd9-c9b4-513c1e40dd2a@gmail.com> (raw)
In-Reply-To: <323291d3-64ae-4648-a731-e695dab2df04@gmail.com>

On 21.05.2016 02:20, Gabriel C wrote:

> On 20.05.2016 12:08, Gabriel C wrote:
>
>>> Does it work when you disable CONFIG_BLK_DEV_INITRD in there?
>> I can test this when I'm home since I need to change the config a bit.
>
> I got to test an kernel without CONFIG_BLK_DEV_INITRD and this way 
> does work.
>

While that worked I read the code not sure I get this right but:

scan_microcode() has :

...
       if (!size) {
         if (!load_builtin_intel_microcode(&cd))
             return UCODE_ERROR;
     } else {
         cd = find_cpio_data(p, (void *)start, size, &offset);
         if (!cd.data)
             return UCODE_ERROR;
     }

...

So when I get this correctly load_builtin_intel_microcode() only works 
on !initrd ?

Should this check not be the other way around ?

something like :

       cd = find_cpio_data(p, (void *)start, size, &offset);
       if (!cd.data) {
            if (!load_builtin_intel_microcode(&cd))
                  return UCODE_ERROR;
       }


Regards,

Gabriel C

  reply	other threads:[~2016-05-21  2:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 10:08 Gabriel C
2016-05-20 10:23 ` Borislav Petkov
2016-05-20 16:03 ` Gabriel C
2016-05-21  0:20 ` Gabriel C
2016-05-21  2:59   ` Gabriel C [this message]
2016-05-21  7:51     ` Borislav Petkov
2016-05-25  9:31       ` Borislav Petkov
2016-05-25 13:48         ` Jim Bos
2016-05-25 14:57           ` Borislav Petkov
2016-05-25 21:29         ` Gabriel C
2016-05-25 21:38           ` Borislav Petkov
2016-05-25 21:50             ` Gabriel C
2016-05-25 23:36               ` Gabriel C
2016-05-26 10:03                 ` Borislav Petkov
2016-05-26 11:52                   ` Gabriel C
2016-05-26 12:46                     ` Borislav Petkov
2016-06-03  8:02                       ` Borislav Petkov
2016-06-04  0:37                         ` Gabriel C
2016-06-04  6:35                           ` Borislav Petkov
2016-05-21  7:45   ` Borislav Petkov
     [not found] <CAEJqkgjFWak5fUc_zR4v-BDgAnjU0NtRfUDDPaEVGjjbEZoqUQ@mail.gmail.com>
2016-05-20  8:36 ` Borislav Petkov
  -- strict thread matches above, loose matches on Subject: below --
2016-05-20  0:55 Gabriel C

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=86dacf1e-83ca-8dd9-c9b4-513c1e40dd2a@gmail.com \
    --to=nix.or.die@gmail.com \
    --cc=bp@suse.de \
    --cc=linux-kernel@vger.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

Powered by JetHome