From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Junichi Nomura <j-nomura@ce.jp.nec.com>,
dyoung@redhat.com, Kairui Song <kasong@redhat.com>,
Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, Chao Fan <fanc.fnst@cn.fujitsu.com>,
"x86@kernel.org" <x86@kernel.org>,
"kexec@lists.infradead.org" <kexec@lists.infradead.org>
Subject: Re: [RFC PATCH] kexec, x86/boot: map systab region in identity mapping before accessing it
Date: Fri, 26 Apr 2019 18:16:35 +0800 [thread overview]
Message-ID: <20190426101635.GQ3584@localhost.localdomain> (raw)
In-Reply-To: <20190426095800.GB4608@zn.tnic>
On 04/26/19 at 11:58am, Borislav Petkov wrote:
> On Fri, Apr 26, 2019 at 05:51:34PM +0800, Baoquan He wrote:
> > I can make a patch to add a bit into xloadflags, to indicate that this
> > is kexec-ed kernel. It can help to differentiate kexec-ed kernel from
> > kdump kernel.
>
> From the recent snafu, the only thing we needed is to differentiate
> between the *first* kernel and the following kernel(s) which has been
> started/loaded using a kexec syscall.
OK. To make sure I got it, the loader type 0xD is enough for this, right?
It's fine to me, we can add it later if needed. I remember there's an
issue in intel/amd iommu, in which we need differentiate between
kexec/kdump kernel, but not very sure. I will check it when I have time
to work on that.
Thanks
Baoquan
next prev parent reply other threads:[~2019-04-26 10:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-19 10:17 [RFC PATCH] kexec, x86/boot: map systab region in identity mapping before accessing it Borislav Petkov
2019-04-19 10:50 ` Baoquan He
2019-04-19 10:55 ` Baoquan He
2019-04-19 11:20 ` Kairui Song
2019-04-19 11:34 ` Borislav Petkov
2019-04-19 11:50 ` Kairui Song
2019-04-19 14:19 ` [PATCH] x86/boot: Disable RSDP parsing temporarily Borislav Petkov
2019-04-22 9:46 ` [tip:x86/urgent] " tip-bot for Borislav Petkov
2019-04-19 11:28 ` [RFC PATCH] kexec, x86/boot: map systab region in identity mapping before accessing it Borislav Petkov
2019-04-19 11:36 ` Borislav Petkov
2019-04-22 14:33 ` Baoquan He
2019-04-22 15:17 ` Borislav Petkov
2019-04-26 9:51 ` Baoquan He
2019-04-26 9:58 ` Borislav Petkov
2019-04-26 10:16 ` Baoquan He [this message]
2019-04-19 11:44 ` Baoquan He
-- strict thread matches above, loose matches on Subject: below --
2019-04-16 9:52 [PATCH] x86/boot: Use efi_setup_data for searching RSDP on kexec-ed kernels Borislav Petkov
2019-04-19 8:34 ` [RFC PATCH] kexec, x86/boot: map systab region in identity mapping before accessing it Kairui Song
2019-04-19 8:58 ` Baoquan He
2019-04-19 9:39 ` Kairui Song
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=20190426101635.GQ3584@localhost.localdomain \
--to=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=fanc.fnst@cn.fujitsu.com \
--cc=hpa@zytor.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=kasong@redhat.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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