From: Pratyush Yadav <pratyush@kernel.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: Pratyush Yadav <pratyush@kernel.org>,
ranxiaokai627@163.com, graf@amazon.com, rppt@kernel.org,
pasha.tatashin@soleen.com, akpm@linux-foundation.org,
kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ran.xiaokai@zte.com.cn
Subject: Re: [PATCH v2] kho: init alloc tags when restoring pages from reserved memory
Date: Fri, 16 Jan 2026 11:26:14 +0000 [thread overview]
Message-ID: <2vxzwm1h7q95.fsf@kernel.org> (raw)
In-Reply-To: <CAJuCfpE3ffje9qXdwB3QZsyE+rD-unChSNXPfrijSkk5Nrt5CQ@mail.gmail.com> (Suren Baghdasaryan's message of "Wed, 14 Jan 2026 14:03:30 -0800")
On Wed, Jan 14 2026, Suren Baghdasaryan wrote:
> On Wed, Jan 14, 2026 at 10:42 AM Pratyush Yadav <pratyush@kernel.org> wrote:
>>
>> On Wed, Jan 14 2026, Suren Baghdasaryan wrote:
[...]
>> So I think you do need to initialize the tags for kho_restore_pages().
>>
>> I sent a patch [0] simplifying the page init logic a bit. I need to do a
>> v2 but it is a very simple change so I can get that done tomorrow. I
>> think it would be good to base your series on that since that would make
>> it easier for you to modify only the kho_restore_pages() path and the
>> end result would be cleaner.
>>
>> [0] https://lore.kernel.org/linux-mm/20251223104448.195589-1-pratyush@kernel.org/
>
> Ok, let's wait for your patch to see the final result. Please CC us
> when you send it.
I sent it out just now:
https://lore.kernel.org/linux-mm/20260116112217.915803-1-pratyush@kernel.org/T/#u
Feel free to use it as the base. Once Andrew picks it up, it should show
up in mm-nonmm-unstable too.
[...]
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2026-01-16 11:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-13 3:34 [PATCH v2] kho: init alloc tags when restoring pages from reserved memory ranxiaokai627
2026-01-13 16:21 ` Pasha Tatashin
2026-01-14 16:55 ` Pratyush Yadav
2026-01-14 17:59 ` Suren Baghdasaryan
2026-01-14 18:42 ` Pratyush Yadav
2026-01-14 22:03 ` Suren Baghdasaryan
2026-01-16 11:26 ` Pratyush Yadav [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=2vxzwm1h7q95.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=graf@amazon.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pasha.tatashin@soleen.com \
--cc=ran.xiaokai@zte.com.cn \
--cc=ranxiaokai627@163.com \
--cc=rppt@kernel.org \
--cc=surenb@google.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.