All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Borislav Petkov <bp@alien8.de>, Thomas Gleixner <tglx@linutronix.de>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] x86/microcode for 6.7
Date: Sat, 11 Nov 2023 14:19:00 -0800	[thread overview]
Message-ID: <CAHk-=wg=+8rceshMkB4VnKxmRccVLtBLPBawnewZuuqyx5U=3A@mail.gmail.com> (raw)
In-Reply-To: <20231103110600.GAZUTUGFjhoLm1KZzE@fat_crate.local>

On Fri, 3 Nov 2023 at 04:06, Borislav Petkov <bp@alien8.de> wrote:
>
> I believe this is the last tip branch from the lineup this merge window.
> It has a lot of nice things, it has been tested on everything we have
> access to so it should be good.

Well, I only now looked more closely at dmesg (because I was testing
an entirely unrelated patch of mine), and I see this:

    smpboot: x86: Booting SMP configuration:
    .... node  #0, CPUs:        #1  #2  #3  #4  #5
    microcode: CPU4: new patch_level=0x0830107a
      #6
    microcode: CPU5: new patch_level=0x0830107a
      #7
    microcode: CPU1: new patch_level=0x0830107a
    microcode: CPU2: new patch_level=0x0830107a
    microcode: CPU3: new patch_level=0x0830107a
    microcode: CPU6: new patch_level=0x0830107a
      #8
    ...
      #63
    microcode: CPU62: new patch_level=0x0830107a
    microcode: CPU63: new patch_level=0x0830107a
    smp: Brought up 1 node, 64 CPUs
    ...
    mip6: Mobile IPv6
    NET: Registered PF_PACKET protocol family
    microcode: microcode updated early to new patch_level=0x0830107a
    microcode: CPU0: patch_level=0x0830107a
    microcode: CPU1: patch_level=0x0830107a
    microcode: CPU2: patch_level=0x0830107a
    ..
    microcode: CPU62: patch_level=0x0830107a
    microcode: CPU63: patch_level=0x0830107a
    microcode: Microcode Update Driver: v2.2.

which is really quite ugly and entirely pointless.

I *really* don't want to be told 129 times that my microcode has been
updated to the same level.

And yes, it's "only" 129 times, because while there are two of those
microcode update lines:

    microcode: microcode updated early to new patch_level=0x0830107a
    microcode: Microcode Update Driver: v2.2.

CPU#0 is only mentioned once, while CPU's 1..63 all get two mentions
(once for the bringup, once fro the summary).

Can we please stop doing this insanity? It's not helpful.

                 Linus

  parent reply	other threads:[~2023-11-11 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-03 11:06 [GIT PULL] x86/microcode for 6.7 Borislav Petkov
2023-11-04 19:01 ` pr-tracker-bot
2023-11-11 22:19 ` Linus Torvalds [this message]
2023-11-11 22:35   ` Borislav Petkov
2023-11-12 12:23     ` Borislav Petkov
2023-11-12 19:41       ` Linus Torvalds
2023-11-12 19:56         ` 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='CAHk-=wg=+8rceshMkB4VnKxmRccVLtBLPBawnewZuuqyx5U=3A@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.