From: David Woodhouse <dwmw2@infradead.org>
To: Alexander Graf <graf@amazon.com>, kexec@lists.infradead.org
Cc: linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
nh-open-source@amazon.com
Subject: Re: [PATCH] kexec: Enable CMA based contiguous allocation
Date: Sat, 24 May 2025 11:16:03 +0100 [thread overview]
Message-ID: <0fac5973d5588ee441ae95384d2edda69989ac10.camel@infradead.org> (raw)
In-Reply-To: <20250512225752.11687-1-graf@amazon.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
On Mon, 2025-05-12 at 22:57 +0000, Alexander Graf wrote:
>
> --- a/include/uapi/linux/kexec.h
> +++ b/include/uapi/linux/kexec.h
> @@ -27,6 +27,7 @@
> #define KEXEC_FILE_ON_CRASH 0x00000002
> #define KEXEC_FILE_NO_INITRAMFS 0x00000004
> #define KEXEC_FILE_DEBUG 0x00000008
> +#define KEXEC_FILE_NO_CMA 0x00000010
>
Gives me EINVAL when I try to use it. This helps (but should it be
permitted only on architectures which implement it?):
--- a/include/linux/kexec.h
+++ b/include/linux/kexec.h
@@ -385,7 +385,7 @@ extern int kexec_load_disabled;
/* List of defined/legal kexec file flags */
#define KEXEC_FILE_FLAGS (KEXEC_FILE_UNLOAD | KEXEC_FILE_ON_CRASH | \
KEXEC_FILE_NO_INITRAMFS | \
- KEXEC_FILE_COOPERATIVE)
+ KEXEC_FILE_COOPERATIVE | KEXEC_FILE_NO_CMA)
/* Location of a reserved region to hold the crash kernel.
*/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]
prev parent reply other threads:[~2025-05-24 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 22:57 Alexander Graf
2025-05-12 23:59 ` Andrew Morton
2025-05-13 2:02 ` David Woodhouse
2025-05-13 3:14 ` Andrew Morton
2025-05-13 8:20 ` Alexander Graf
2025-05-24 10:16 ` David Woodhouse [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=0fac5973d5588ee441ae95384d2edda69989ac10.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nh-open-source@amazon.com \
--cc=pasha.tatashin@soleen.com \
/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
all inboxes | Powered by JetHome®