From: Thomas Gleixner <tglx@linutronix.de>
To: speck@linutronix.de
Subject: Re: [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2
Date: Sat, 19 May 2018 10:33:48 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.21.1805191023070.1599@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20180518203401.GK23713@char.us.oracle.com>
On Fri, 18 May 2018, speck for Konrad Rzeszutek Wilk wrote:
> On Fri, May 18, 2018 at 09:57:47PM +0200, speck for Thomas Gleixner wrote:
> > > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > > (XEN) 0000000000000000 0000000000000000 0000000000000000 0000000000000000
> > > (XEN) 0f00000060c0c748 ccccccccccccc305 cccccccccccccccc cccccccccccccccc
> > > (XEN) Hardware Dom0 crashed: rebooting machine in 5 seconds.
> > > (XEN) APIC error on CPU0: 40(00)
> >
> > The above is pretty useless and undecodable. So what makes Dom0 crash in a
> > way that the machine needs to be rebooted? The call to get_cpu_cap()?
>
> Yup. B/c there is no early callback installed yet and it ends up using 'cli'
Sigh, 'using CLI' is not helpful either. The callchain and where the CLI is
invoked, is the interesting information.
But well, as you say its get_cpu_cap() I went and stared at it for while,
but there is absolutely NOTHING which might invoke CLI. It was nothing
before SSB and SSB did not add anything either.
So this patch is voodoo and makes exactly zero sense, unless you come up
with some sensible explanation.
Thanks,
tglx
prev parent reply other threads:[~2018-05-19 8:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 3:18 [MODERATED] [PATCH v17.1 2/2] [PATCH v17.1 2/2] SSB Fix #2 konrad.wilk
2018-05-18 8:20 ` [MODERATED] " Greg KH
2018-05-18 9:02 ` Thomas Gleixner
2018-05-18 11:46 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 9:14 ` Thomas Gleixner
2018-05-18 11:43 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 12:03 ` Greg KH
2018-05-18 13:21 ` Greg KH
2018-05-18 18:22 ` Konrad Rzeszutek Wilk
2018-05-18 19:57 ` Thomas Gleixner
2018-05-18 20:34 ` [MODERATED] " Konrad Rzeszutek Wilk
2018-05-18 20:40 ` Linus Torvalds
2018-05-18 21:05 ` Konrad Rzeszutek Wilk
2018-05-18 21:10 ` Linus Torvalds
2018-05-19 8:33 ` Thomas Gleixner [this message]
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=alpine.DEB.2.21.1805191023070.1599@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=speck@linutronix.de \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).