Xen project Mailing List

Re: [Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0

To: Jan Beulich <JBeulich@xxxxxxxx>, Andy Smith <andy@xxxxxxxxxxxxxx>

From: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Date: Mon, 22 Jul 2019 13:06:03 +0100

Authentication-results: esa1.hc3370-68.iphmx.com; dkim=none (message not signed) header.i=none; spf=None smtp.pra=andrew.cooper3@xxxxxxxxxx; spf=Pass smtp.mailfrom=Andrew.Cooper3@xxxxxxxxxx; spf=None smtp.helo=postmaster@xxxxxxxxxxxxxxx

Autocrypt: addr=andrew.cooper3@xxxxxxxxxx; prefer-encrypt=mutual; keydata= mQINBFLhNn8BEADVhE+Hb8i0GV6mihnnr/uiQQdPF8kUoFzCOPXkf7jQ5sLYeJa0cQi6Penp VtiFYznTairnVsN5J+ujSTIb+OlMSJUWV4opS7WVNnxHbFTPYZVQ3erv7NKc2iVizCRZ2Kxn srM1oPXWRic8BIAdYOKOloF2300SL/bIpeD+x7h3w9B/qez7nOin5NzkxgFoaUeIal12pXSR Q354FKFoy6Vh96gc4VRqte3jw8mPuJQpfws+Pb+swvSf/i1q1+1I4jsRQQh2m6OTADHIqg2E ofTYAEh7R5HfPx0EXoEDMdRjOeKn8+vvkAwhviWXTHlG3R1QkbE5M/oywnZ83udJmi+lxjJ5 YhQ5IzomvJ16H0Bq+TLyVLO/VRksp1VR9HxCzItLNCS8PdpYYz5TC204ViycobYU65WMpzWe LFAGn8jSS25XIpqv0Y9k87dLbctKKA14Ifw2kq5OIVu2FuX+3i446JOa2vpCI9GcjCzi3oHV e00bzYiHMIl0FICrNJU0Kjho8pdo0m2uxkn6SYEpogAy9pnatUlO+erL4LqFUO7GXSdBRbw5 gNt25XTLdSFuZtMxkY3tq8MFss5QnjhehCVPEpE6y9ZjI4XB8ad1G4oBHVGK5LMsvg22PfMJ ISWFSHoF/B5+lHkCKWkFxZ0gZn33ju5n6/FOdEx4B8cMJt+cWwARAQABtClBbmRyZXcgQ29v cGVyIDxhbmRyZXcuY29vcGVyM0BjaXRyaXguY29tPokCOgQTAQgAJAIbAwULCQgHAwUVCgkI CwUWAgMBAAIeAQIXgAUCWKD95wIZAQAKCRBlw/kGpdefoHbdD/9AIoR3k6fKl+RFiFpyAhvO 59ttDFI7nIAnlYngev2XUR3acFElJATHSDO0ju+hqWqAb8kVijXLops0gOfqt3VPZq9cuHlh IMDquatGLzAadfFx2eQYIYT+FYuMoPZy/aTUazmJIDVxP7L383grjIkn+7tAv+qeDfE+txL4 SAm1UHNvmdfgL2/lcmL3xRh7sub3nJilM93RWX1Pe5LBSDXO45uzCGEdst6uSlzYR/MEr+5Z JQQ32JV64zwvf/aKaagSQSQMYNX9JFgfZ3TKWC1KJQbX5ssoX/5hNLqxMcZV3TN7kU8I3kjK mPec9+1nECOjjJSO/h4P0sBZyIUGfguwzhEeGf4sMCuSEM4xjCnwiBwftR17sr0spYcOpqET ZGcAmyYcNjy6CYadNCnfR40vhhWuCfNCBzWnUW0lFoo12wb0YnzoOLjvfD6OL3JjIUJNOmJy RCsJ5IA/Iz33RhSVRmROu+TztwuThClw63g7+hoyewv7BemKyuU6FTVhjjW+XUWmS/FzknSi dAG+insr0746cTPpSkGl3KAXeWDGJzve7/SBBfyznWCMGaf8E2P1oOdIZRxHgWj0zNr1+ooF /PzgLPiCI4OMUttTlEKChgbUTQ+5o0P080JojqfXwbPAyumbaYcQNiH1/xYbJdOFSiBv9rpt TQTBLzDKXok86LkCDQRS4TZ/ARAAkgqudHsp+hd82UVkvgnlqZjzz2vyrYfz7bkPtXaGb9H4 Rfo7mQsEQavEBdWWjbga6eMnDqtu+FC+qeTGYebToxEyp2lKDSoAsvt8w82tIlP/EbmRbDVn 7bhjBlfRcFjVYw8uVDPptT0TV47vpoCVkTwcyb6OltJrvg/QzV9f07DJswuda1JH3/qvYu0p vjPnYvCq4NsqY2XSdAJ02HrdYPFtNyPEntu1n1KK+gJrstjtw7KsZ4ygXYrsm/oCBiVW/OgU g/XIlGErkrxe4vQvJyVwg6YH653YTX5hLLUEL1NS4TCo47RP+wi6y+TnuAL36UtK/uFyEuPy wwrDVcC4cIFhYSfsO0BumEI65yu7a8aHbGfq2lW251UcoU48Z27ZUUZd2Dr6O/n8poQHbaTd 6bJJSjzGGHZVbRP9UQ3lkmkmc0+XCHmj5WhwNNYjgbbmML7y0fsJT5RgvefAIFfHBg7fTY/i kBEimoUsTEQz+N4hbKwo1hULfVxDJStE4sbPhjbsPCrlXf6W9CxSyQ0qmZ2bXsLQYRj2xqd1 bpA+1o1j2N4/au1R/uSiUFjewJdT/LX1EklKDcQwpk06Af/N7VZtSfEJeRV04unbsKVXWZAk uAJyDDKN99ziC0Wz5kcPyVD1HNf8bgaqGDzrv3TfYjwqayRFcMf7xJaL9xXedMcAEQEAAYkC HwQYAQgACQUCUuE2fwIbDAAKCRBlw/kGpdefoG4XEACD1Qf/er8EA7g23HMxYWd3FXHThrVQ HgiGdk5Yh632vjOm9L4sd/GCEACVQKjsu98e8o3ysitFlznEns5EAAXEbITrgKWXDDUWGYxd pnjj2u+GkVdsOAGk0kxczX6s+VRBhpbBI2PWnOsRJgU2n10PZ3mZD4Xu9kU2IXYmuW+e5KCA vTArRUdCrAtIa1k01sPipPPw6dfxx2e5asy21YOytzxuWFfJTGnVxZZSCyLUO83sh6OZhJkk b9rxL9wPmpN/t2IPaEKoAc0FTQZS36wAMOXkBh24PQ9gaLJvfPKpNzGD8XWR5HHF0NLIJhgg 4ZlEXQ2fVp3XrtocHqhu4UZR4koCijgB8sB7Tb0GCpwK+C4UePdFLfhKyRdSXuvY3AHJd4CP 4JzW0Bzq/WXY3XMOzUTYApGQpnUpdOmuQSfpV9MQO+/jo7r6yPbxT7CwRS5dcQPzUiuHLK9i nvjREdh84qycnx0/6dDroYhp0DFv4udxuAvt1h4wGwTPRQZerSm4xaYegEFusyhbZrI0U9tJ B8WrhBLXDiYlyJT6zOV2yZFuW47VrLsjYnHwn27hmxTC/7tvG3euCklmkn9Sl9IAKFu29RSo d5bD8kMSCYsTqtTfT6W4A3qHGvIDta3ptLYpIAOD2sY3GYq2nf3Bbzx81wZK14JdDDHUX2Rs 6+ahAA==

Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>

Delivery-date: Mon, 22 Jul 2019 12:06:12 +0000

Ironport-sdr: NxDMOnkzsyLGnPWmWPjZrbjaIiAka7ahdEY8+DiPM9EvGCTiP2GJHnnDh7t35B2RafI4SnjoTf NbabBYM3eG8C60x+5gvEsd5ZmjyyjYRSnUd0V6kb3vfefzfWC6GWYmhQIGWoksGT/7lYKuKi3r qqufQZWvo/JGqgiuy/LiIKCRjnyt24GD7dJdXmuiWmPtgAM+dURUM0DgK/IMVko//VPsafihwK /bnLxiuFn/YFga9vkSIeuQensfXyGlV19v7mxdT66h6bDa1cENWLcLe/DPMwUTstGZXa0q/1F7 nGE=

List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Openpgp: preference=signencrypt

On 22/07/2019 10:16, Jan Beulich wrote: > On 21.07.2019 22:06, Andy Smith wrote: >> 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. > "Expected" isn't the right word. I've noticed this too on one or two > occasions, and I can't (yet) explain what's going on there, the more > that so far (including your report) this is only ever for the first > CPU to get re-offlined. Something to be looked into as time permits. Does reverting back to credit1 make the issue go away? I've never encountered this on any smt=0 test, but I also don't use credit2 at all. The sibling threads shouldn't be inserted into the scheduler in the first place, and I thought we took deliberate steps to prevent that from occurring. ~Andrew _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.