From: Baoquan He <bhe@redhat.com>
To: Sourabh Jain <sourabhjain@linux.ibm.com>, akpm@linux-foundation.org
Cc: Qiang Ma <maqianga@uniontech.com>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
shivang upadhyay <shivangu@linux.ibm.com>
Subject: Re: [PATCH v3 0/3] kexec: print out debugging message if required for kexec_load
Date: Thu, 27 Nov 2025 23:30:36 +0800 [thread overview]
Message-ID: <aShunGBgVbEZmCxO@MiWiFi-R3L-srv> (raw)
In-Reply-To: <7aadda55-d2a4-40f9-95ef-d284ec358646@linux.ibm.com>
On 11/27/25 at 05:31pm, Sourabh Jain wrote:
> Hello All,
>
> Do we have plan to support KEXEC_DEBUG flag?
>
> Because upstream kexec-tools already added support for KEXEC_DEBUG flag
> and that breaks the kexec_load with -d option.
>
> - kexec: add kexec flag to support debug printing
> https://git.kernel.org/pub/scm/utils/kernel/kexec/kexec-tools.git/commit/?id=71d6fd99af7e
I think we should revert that kexec-tools commit. This whole patchset is
non-sense. Because of my carelessness, that userspace patch was merged.
Hi Sourabh,
Could you go through this patchset and help check if they are really
needed? I can't find anything to convince myself. Thanks.
next prev parent reply other threads:[~2025-11-27 15:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-26 8:44 [PATCH v3 0/3] kexec: print out debugging message if required for kexec_load Qiang Ma
2025-11-26 8:44 ` [PATCH v3 1/3] kexec: Fix uninitialized struct kimage *image pointer Qiang Ma
2025-11-26 8:44 ` [PATCH v3 2/3] kexec: add kexec flag to control debug printing Qiang Ma
2025-11-26 8:44 ` [PATCH v3 3/3] kexec: print out debugging message if required for kexec_load Qiang Ma
2025-11-27 1:47 ` [PATCH v3 0/3] " Baoquan He
2025-11-27 2:04 ` Qiang Ma
2025-11-27 2:36 ` Baoquan He
2025-11-27 3:00 ` Qiang Ma
2025-11-27 3:55 ` Baoquan He
2025-11-27 6:59 ` Qiang Ma
2025-11-27 12:01 ` Sourabh Jain
2025-11-27 15:30 ` Baoquan He [this message]
2025-11-28 9:41 ` Sourabh Jain
2025-11-30 2:56 ` Baoquan He
2025-12-04 12:18 ` Sourabh Jain
2025-12-05 9:20 ` Qiang Ma
2025-12-09 0:45 ` Baoquan He
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=aShunGBgVbEZmCxO@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maqianga@uniontech.com \
--cc=shivangu@linux.ibm.com \
--cc=sourabhjain@linux.ibm.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