From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Baoquan He <bhe@redhat.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de,
mingo@kernel.org, bp@alien8.de, hpa@zytor.com,
kirill.shutemov@linux.intel.com, dyoung@redhat.com,
x86@kernel.org, kexec@lists.infradead.org
Subject: Re: [PATCH RESEND 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel
Date: Fri, 25 Jan 2019 15:05:27 +0300 [thread overview]
Message-ID: <20190125120527.3n6pqt5zzvczkct6@kshutemo-mobl1> (raw)
In-Reply-To: <20190125022817.29506-1-bhe@redhat.com>
On Fri, Jan 25, 2019 at 10:28:14AM +0800, Baoquan He wrote:
> This is a RESEND post.
>
> The original v1 post can be found here:
> http://lkml.kernel.org/r/20180829141624.13985-1-bhe@redhat.com
>
> It's trying to fix several corner case issues for kexec/kdump when
> dynamic switching of paging mode is enabled in x86_64. Please click
> above link to check the details.
>
> In v1, hpa raised concern that why the paging mode checking is not done
> before kexec jumping, the discussion can be found here:
>
> http://lkml.kernel.org/r/alpine.DEB.2.21.1809051002020.1416@nanos.tec.linutronix.de
>
> As tglx said, it might be not doable for kdump since kdump kernel's
> reserved crashkernel region only owns a portion of memory, may
> be above 4G; and might be not safer to do paging mode checking and
> switching thing after crash.
>
> So resend this patchset.
Changes look good to me:
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
--
Kirill A. Shutemov
WARNING: multiple messages have this Message-ID (diff)
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Baoquan He <bhe@redhat.com>
Cc: x86@kernel.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, bp@alien8.de, hpa@zytor.com,
tglx@linutronix.de, dyoung@redhat.com, mingo@kernel.org,
kirill.shutemov@linux.intel.com
Subject: Re: [PATCH RESEND 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel
Date: Fri, 25 Jan 2019 15:05:27 +0300 [thread overview]
Message-ID: <20190125120527.3n6pqt5zzvczkct6@kshutemo-mobl1> (raw)
In-Reply-To: <20190125022817.29506-1-bhe@redhat.com>
On Fri, Jan 25, 2019 at 10:28:14AM +0800, Baoquan He wrote:
> This is a RESEND post.
>
> The original v1 post can be found here:
> http://lkml.kernel.org/r/20180829141624.13985-1-bhe@redhat.com
>
> It's trying to fix several corner case issues for kexec/kdump when
> dynamic switching of paging mode is enabled in x86_64. Please click
> above link to check the details.
>
> In v1, hpa raised concern that why the paging mode checking is not done
> before kexec jumping, the discussion can be found here:
>
> http://lkml.kernel.org/r/alpine.DEB.2.21.1809051002020.1416@nanos.tec.linutronix.de
>
> As tglx said, it might be not doable for kdump since kdump kernel's
> reserved crashkernel region only owns a portion of memory, may
> be above 4G; and might be not safer to do paging mode checking and
> switching thing after crash.
>
> So resend this patchset.
Changes look good to me:
Acked-by: Kirill A. Shutemov <kirill.shutemov@linux.intel.com>
--
Kirill A. Shutemov
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next prev parent reply other threads:[~2019-01-25 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-25 2:28 [PATCH RESEND 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Baoquan He
2019-01-25 2:28 ` Baoquan He
2019-01-25 2:28 ` [PATCH RESEND 1/3] x86/boot: Add bit fields into xloadflags for 5-level kernel checking Baoquan He
2019-01-25 2:28 ` Baoquan He
2019-01-29 20:05 ` Thomas Gleixner
2019-01-29 20:05 ` Thomas Gleixner
2019-02-11 7:02 ` Baoquan He
2019-02-11 7:02 ` Baoquan He
2019-02-11 7:40 ` [PATCH v2 1/3] x86/boot: Add xloadflags bits " Baoquan He
2019-02-11 7:40 ` Baoquan He
2019-01-25 2:28 ` [PATCH RESEND 2/3] x86/kexec/64: Error out if try to jump to old 4-level kernel from 5-level kernel Baoquan He
2019-01-25 2:28 ` Baoquan He
2019-01-25 2:28 ` [PATCH RESEND 3/3] x86/kdump/64: Change the upper limit of crashkernel reservation Baoquan He
2019-01-25 2:28 ` Baoquan He
2019-01-25 12:05 ` Kirill A. Shutemov [this message]
2019-01-25 12:05 ` [PATCH RESEND 0/3] Add restrictions for kexec/kdump jumping between 5-level and 4-level kernel Kirill A. Shutemov
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=20190125120527.3n6pqt5zzvczkct6@kshutemo-mobl1 \
--to=kirill@shutemov.name \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=kexec@lists.infradead.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@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 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.