From: Tarun Sahu <tarunsahu@google.com>
To: Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Alexander Graf <graf@amazon.com>
Cc: kexec@lists.infradead.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, Tarun Sahu <tarunsahu@google.com>
Subject: [PATCH v5 2/3] kho: add KHOSER_COPY_PTR to allow phys copy of serialized ptr
Date: Tue, 23 Jun 2026 10:52:00 +0000 [thread overview]
Message-ID: <20260623105201.3724592-3-tarunsahu@google.com> (raw)
In-Reply-To: <20260623105201.3724592-1-tarunsahu@google.com>
Adding KHOSER_COPY_PTR to copy one serializeable pointer to
another. It basically allows copy of phys val of the
serializeable pointer.
It ignores the typecheck if any of the argument is of void *
Signed-off-by: Tarun Sahu <tarunsahu@google.com>
---
include/linux/kho/abi/kexec_handover.h | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/include/linux/kho/abi/kexec_handover.h b/include/linux/kho/abi/kexec_handover.h
index 5e2eb8519bda..c1b61d875dcc 100644
--- a/include/linux/kho/abi/kexec_handover.h
+++ b/include/linux/kho/abi/kexec_handover.h
@@ -139,6 +139,17 @@
(typeof((s).ptr))((s).phys ? phys_to_virt((s).phys) : NULL); \
})
+/* Copies one serializable pointer to another. */
+#define KHOSER_COPY_PTR(dest, src) \
+ ({ \
+ static_assert( \
+ __builtin_types_compatible_p(typeof((dest).ptr), typeof((src).ptr)) || \
+ __builtin_types_compatible_p(typeof((dest).ptr), void *) || \
+ __builtin_types_compatible_p(typeof((src).ptr), void *), \
+ "pointer type mismatch in KHOSER_COPY_PTR" \
+ ); \
+ (dest).phys = (src).phys; \
+ })
/*
* This header is embedded at the beginning of each `kho_vmalloc_chunk`
* and contains a pointer to the next chunk in the linked list,
--
2.55.0.rc0.786.g65d90a0328-goog
next prev parent reply other threads:[~2026-06-23 10:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-23 10:51 [PATCH v5 0/2] luo: convert serialized ptr to KHOSER_PTR Tarun Sahu
2026-06-23 10:51 ` [PATCH v5 1/3] mm/memfd_luo: validate serialized_data before conversion Tarun Sahu
2026-06-23 12:19 ` Pratyush Yadav
2026-06-23 10:52 ` Tarun Sahu [this message]
2026-06-23 11:12 ` [PATCH v5 2/3] kho: add KHOSER_COPY_PTR to allow phys copy of serialized ptr tarunsahu
2026-06-23 12:26 ` Pratyush Yadav
2026-06-23 10:52 ` [PATCH v5 3/3] luo: Update serialized data to use KHOSER_PTR Tarun Sahu
2026-06-23 11:12 ` tarunsahu
2026-06-23 12:54 ` Pratyush Yadav
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=20260623105201.3724592-3-tarunsahu@google.com \
--to=tarunsahu@google.com \
--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=pratyush@kernel.org \
--cc=rppt@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.