All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Smith <andy@strugglers.net>
To: xen-devel <xen-devel@lists.xenproject.org>
Subject: [Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0
Date: Sun, 21 Jul 2019 20:06:23 +0000	[thread overview]
Message-ID: <20190721200623.GJ11726@bitfolk.com> (raw)

Hi,

My first time using smt=0 on hypervisor command line so not sure how
many versions and different pieces of hardware this happens with,
but I noticed this during the microcode update stage of boot:

(XEN) HVM: HAP page sizes: 4kB, 2MB, 1GB
(XEN) Adding cpu 1 to runqueue 0
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) CPU 1 still not dead...
(XEN) Removing cpu 1 from runqueue 0
(XEN) microcode: CPU2 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 2 to runqueue 0
(XEN) Adding cpu 3 to runqueue 0
(XEN) Removing cpu 3 from runqueue 0
(XEN) microcode: CPU4 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 4 to runqueue 0
(XEN) Adding cpu 5 to runqueue 0
(XEN) Removing cpu 5 from runqueue 0
(XEN) microcode: CPU6 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 6 to runqueue 0
(XEN) Adding cpu 7 to runqueue 0
(XEN) Removing cpu 7 from runqueue 0
(XEN) microcode: CPU8 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 8 to runqueue 0
(XEN) Adding cpu 9 to runqueue 0
(XEN) Removing cpu 9 from runqueue 0
(XEN) microcode: CPU10 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 10 to runqueue 0
(XEN) Adding cpu 11 to runqueue 0
(XEN) Removing cpu 11 from runqueue 0
(XEN) microcode: CPU12 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 12 to runqueue 0
(XEN) Adding cpu 13 to runqueue 0
(XEN) Removing cpu 13 from runqueue 0
(XEN) microcode: CPU14 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02 
(XEN) Adding cpu 14 to runqueue 0
(XEN) Adding cpu 15 to runqueue 0
(XEN) Removing cpu 15 from runqueue 0
(XEN) Brought up 8 CPUs
(XEN) Parked 8 CPUs

It doesn't happen with smt=1 and it also doesn't happen when SMT is
disabled in the BIOS.

Boot does continue normally after this point.

Is this expected? 4.12.

Cheers,
Andy

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

             reply	other threads:[~2019-07-21 20:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-21 20:06 Andy Smith [this message]
2019-07-22  9:16 ` [Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0 Jan Beulich
2019-07-22 12:06   ` Andrew Cooper
2019-07-22 12:18     ` Jan Beulich
2019-07-22 12:55       ` Juergen Gross
2019-08-02  2:15     ` Andy Smith
2019-08-02  4:51       ` Juergen Gross
2019-08-02 10:13         ` Andrew Cooper

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=20190721200623.GJ11726@bitfolk.com \
    --to=andy@strugglers.net \
    --cc=xen-devel@lists.xenproject.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.