From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas.Lendacky@amd.com, x86@kernel.org,
lijiang <lijiang@redhat.com>,
peterz@infradead.org, dave.hansen@linux.intel.com,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
mingo@redhat.com, luto@kernel.org, hpa@zytor.com,
tglx@linutronix.de, dyoung@redhat.com, akpm@linux-foundation.org
Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table
Date: Sat, 8 Jun 2019 18:01:39 +0800 [thread overview]
Message-ID: <20190608100139.GC26148@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190608091030.GB32464@zn.tnic>
On 06/08/19 at 11:10am, Borislav Petkov wrote:
> On Sat, Jun 08, 2019 at 11:54:51AM +0800, Baoquan He wrote:
> > Is it a UEFI box?
>
> Yes.
OK, it doesn't matter with uefi since CONFIG_RANDOMIZE_BASE is not set.
>
> > If it's uefi machine, it should relate to below issue. Because kexec
> > always fails to randomly choose a new position for kernel.
>
> The kernel succeeds in selecting a position for the kernel - the kexec
> kernel doesn't load when a panic happens. Rather, the box panics and
> nothing more.
OK, it may be different with the case we met, if panic happened when
load a kdump kernel.
We can load with 'kexec -l' or 'kexec -p', but can't boot after triggering
crash or execute 'kexec -e' to do kexec jumping.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Baoquan He <bhe@redhat.com>
To: Borislav Petkov <bp@alien8.de>
Cc: lijiang <lijiang@redhat.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
tglx@linutronix.de, mingo@redhat.com, akpm@linux-foundation.org,
dave.hansen@linux.intel.com, luto@kernel.org,
peterz@infradead.org, x86@kernel.org, hpa@zytor.com,
dyoung@redhat.com, Thomas.Lendacky@amd.com
Subject: Re: [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table
Date: Sat, 8 Jun 2019 18:01:39 +0800 [thread overview]
Message-ID: <20190608100139.GC26148@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20190608091030.GB32464@zn.tnic>
On 06/08/19 at 11:10am, Borislav Petkov wrote:
> On Sat, Jun 08, 2019 at 11:54:51AM +0800, Baoquan He wrote:
> > Is it a UEFI box?
>
> Yes.
OK, it doesn't matter with uefi since CONFIG_RANDOMIZE_BASE is not set.
>
> > If it's uefi machine, it should relate to below issue. Because kexec
> > always fails to randomly choose a new position for kernel.
>
> The kernel succeeds in selecting a position for the kernel - the kexec
> kernel doesn't load when a panic happens. Rather, the box panics and
> nothing more.
OK, it may be different with the case we met, if panic happened when
load a kdump kernel.
We can load with 'kexec -l' or 'kexec -p', but can't boot after triggering
crash or execute 'kexec -e' to do kexec jumping.
next prev parent reply other threads:[~2019-06-08 10:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-23 1:30 [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel e820 table Lianbo Jiang
2019-04-23 1:30 ` Lianbo Jiang
2019-04-23 1:30 ` [PATCH 1/3 v11] x86/e820, resource: add a new I/O resource descriptor 'IORES_DESC_RESERVED' Lianbo Jiang
2019-04-23 1:30 ` Lianbo Jiang
2019-06-20 9:59 ` [tip:x86/kdump] x86/e820, ioport: Add a new I/O resource descriptor IORES_DESC_RESERVED tip-bot for Lianbo Jiang
2019-04-23 1:30 ` [PATCH 2/3 v11] x86/mm: change the check condition in SEV because a new descriptor is introduced Lianbo Jiang
2019-04-23 1:30 ` Lianbo Jiang
2019-06-20 10:00 ` [tip:x86/kdump] x86/mm: Rework ioremap resource mapping determination tip-bot for Lianbo Jiang
2019-04-23 1:30 ` [PATCH 3/3 v11] x86/kexec_file: add reserved e820 ranges to kdump kernel e820 table Lianbo Jiang
2019-04-23 1:30 ` Lianbo Jiang
2019-06-20 10:01 ` [tip:x86/kdump] x86/crash: Add e820 reserved ranges to kdump kernel's " tip-bot for Lianbo Jiang
2019-05-28 7:30 ` [PATCH 0/3 v11] add reserved e820 ranges to the kdump kernel " lijiang
2019-05-28 7:30 ` lijiang
2019-06-07 17:42 ` Borislav Petkov
2019-06-07 17:42 ` Borislav Petkov
2019-06-08 3:54 ` Baoquan He
2019-06-08 3:54 ` Baoquan He
2019-06-08 9:10 ` Borislav Petkov
2019-06-08 9:10 ` Borislav Petkov
2019-06-08 10:01 ` Baoquan He [this message]
2019-06-08 10:01 ` Baoquan He
2019-06-08 10:06 ` Borislav Petkov
2019-06-08 10:06 ` Borislav Petkov
2019-06-08 10:26 ` Baoquan He
2019-06-08 10:26 ` Baoquan He
2019-06-10 11:37 ` Borislav Petkov
2019-06-10 11:37 ` Borislav Petkov
2019-06-12 1:14 ` lijiang
2019-06-12 1:14 ` lijiang
2019-06-12 1:55 ` Baoquan He
2019-06-12 1:55 ` Baoquan He
2019-06-12 5:49 ` Dave Young
2019-06-12 5:49 ` Dave Young
2019-06-12 15:10 ` Borislav Petkov
2019-06-12 15:10 ` Borislav Petkov
2019-06-12 16:52 ` Lendacky, Thomas
2019-06-12 16:52 ` Lendacky, Thomas
2019-06-12 18:07 ` Borislav Petkov
2019-06-12 18:07 ` Borislav Petkov
2019-06-12 19:10 ` Lendacky, Thomas
2019-06-12 19:10 ` Lendacky, Thomas
2019-06-13 15:07 ` Baoquan He
2019-06-13 15:07 ` Baoquan He
2019-06-13 1:18 ` dyoung
2019-06-13 1:18 ` dyoung
2019-06-09 4:02 ` lijiang
2019-06-09 4:02 ` lijiang
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=20190608100139.GC26148@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=Thomas.Lendacky@amd.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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 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.