From: Baoquan He <bhe@redhat.com>
To: Alexander Graf <graf@amazon.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Pasha Tatashin <pasha.tatashin@soleen.com>,
nh-open-source@amazon.com,
Zhongkun He <hezhongkun.hzk@bytedance.com>, Bcc: bhe@redhat.com;
Subject: Re: [PATCH v4] kexec: Enable CMA based contiguous allocation
Date: Tue, 10 Jun 2025 07:17:55 +0800 [thread overview]
Message-ID: <aEdroxwd/TOyxxIr@MiWiFi-R3L-srv> (raw)
In-Reply-To: <f609d5a0-99d5-4328-8a18-00f6a9e1a48c@amazon.com>
On 06/09/25 at 09:03am, Alexander Graf wrote:
>
> On 21.05.25 17:29, Alexander Graf wrote:
......
> > Using CMA allocations has two advantages:
> >
> > 1) Faster by 4-50 ms per 100 MiB. There is no more need to copy in the
> > hot phase.
> > 2) More robust. Even if by accident some page is still in use for DMA,
> > the new kernel image will be safe from that access because it resides
> > in a memory region that is considered allocated in the old kernel and
> > has a chance to reinitialize that component.
> >
> > Signed-off-by: Alexander Graf <graf@amazon.com>
>
>
> Ping? Not seeing this patch in Linus' master tree :)
I saw Andrew had added this to his mm-nonmem-unstable, it could be
dropped later because of new version posting.
I would like to ACK this patch, let's see how it's going. One thing is
if IOMMU is on, the devices of no .shutdown method could still be on
flight and look up the IO page table and corrupt kernel, that's another
story.
Acked-by: Baoquan He <bhe@redhat.com>
next prev parent reply other threads:[~2025-06-09 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 15:29 [PATCH v4] kexec: Enable CMA based contiguous allocation Alexander Graf
2025-05-26 3:09 ` Baoquan He
2025-05-26 5:48 ` Alexander Graf
2025-06-09 7:03 ` Alexander Graf
2025-06-09 23:17 ` Baoquan He [this message]
2025-06-09 23:52 ` Andrew Morton
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=aEdroxwd/TOyxxIr@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=hezhongkun.hzk@bytedance.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 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.