From: Ingo Molnar <mingo@kernel.org>
To: Alexandru Chirvasitu <achirvasub@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
kernel list <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Brian Gerst <brgerst@gmail.com>,
Denys Vlasenko <dvlasenk@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Josh Poimboeuf <jpoimboe@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: Re: PROBLEM: consolidated IDT invalidation causes kexec to reboot
Date: Mon, 25 Dec 2017 10:47:46 +0100 [thread overview]
Message-ID: <20171225094746.bcbmqqyjiaioo7lh@gmail.com> (raw)
In-Reply-To: <20171224152715.GA1506@chirva-void>
* Alexandru Chirvasitu <achirvasub@gmail.com> wrote:
> The first attachment is the config I initially used last night after
> that second patch (removing 'local' etc.).
>
> As you guessed, all four options are set, hence the name of the file
> (ending in '-y'). The other config I'm attaching was treated as you
> lay out (2-config-n).
>
> I used the '-n' config to compile two kernels just now:
>
> (a) e802a51, that same first commit giving me trouble.
>
> The changes made no difference to kexec behaviour: with the e802a51
> kernel calling kexec boot directly with -e and triggering a panic both
> kick off a full reboot, though the crash kernel registers as loaded.
>
> (b) the kernel in the branch I made last night, with the set_idt kexec
> (for good measure, I thought I might as well do this one too).
>
> No difference here either: the crash dump kernel boots fine both ways
> (directly and upon intentional crashing).
Thanks for all the info!
Detailed analysis from me (or Thomas) will have to wait after the Christmas
hollidays.
Thanks,
Ingo
next prev parent reply other threads:[~2017-12-25 9:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 1:44 PROBLEM: consolidated IDT invalidation causes kexec to reboot Alexandru Chirvasitu
2017-12-24 3:30 ` Linus Torvalds
2017-12-24 7:28 ` Alexandru Chirvasitu
2017-12-24 11:28 ` Ingo Molnar
2017-12-24 15:27 ` Alexandru Chirvasitu
2017-12-24 16:40 ` Alexandru Chirvasitu
2017-12-25 9:47 ` Ingo Molnar [this message]
2017-12-25 14:40 ` Andy Lutomirski
2017-12-25 21:29 ` Alexandru Chirvasitu
2017-12-26 18:51 ` Linus Torvalds
2017-12-26 19:26 ` hpa
2017-12-26 23:19 ` Alexandru Chirvasitu
2017-12-26 23:39 ` hpa
2017-12-26 23:40 ` hpa
2017-12-26 23:45 ` hpa
2017-12-27 2:16 ` Linus Torvalds
2017-12-27 2:25 ` hpa
2017-12-27 2:54 ` Linus Torvalds
2017-12-27 3:00 ` hpa
2017-12-28 1:30 ` Konrad Rzeszutek Wilk
2017-12-27 4:41 ` Alexandru Chirvasitu
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=20171225094746.bcbmqqyjiaioo7lh@gmail.com \
--to=mingo@kernel.org \
--cc=achirvasub@gmail.com \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox