From: Andy Smith <andy@strugglers.net>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Jan Beulich <JBeulich@suse.com>
Subject: Re: [Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0
Date: Fri, 2 Aug 2019 02:15:29 +0000 [thread overview]
Message-ID: <20190802021529.GR12975@bitfolk.com> (raw)
In-Reply-To: <c33f310d-7956-ba59-7df7-1cdc66aa1979@citrix.com>
Hi,
On Mon, Jul 22, 2019 at 01:06:03PM +0100, Andrew Cooper wrote:
> On 22/07/2019 10:16, Jan Beulich wrote:
> > On 21.07.2019 22:06, Andy Smith wrote:
> >> (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...
[…]
> Does reverting back to credit1 make the issue go away?
Yes, I don't see this with sched=credit, smt=0 and SMT enabled in
the BIOS:
(XEN) microcode: CPU2 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU4 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU6 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU8 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU10 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU12 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) microcode: CPU14 updated from revision 0x2000057 to 0x200005e, date = 2019-04-02
(XEN) Brought up 8 CPUs
(XEN) Parked 8 CPUs
Thanks,
Andy
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-08-02 2:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-21 20:06 [Xen-devel] "CPU N still not dead..." messages during microcode update stage of boot when smt=0 Andy Smith
2019-07-22 9:16 ` 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 [this message]
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=20190802021529.GR12975@bitfolk.com \
--to=andy@strugglers.net \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--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.