From: tarunsahu@google.com
To: Mike Rapoport <rppt@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Alexander Graf <graf@amazon.com>,
Pratyush Yadav <pratyush@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
linux-mm@kvack.org
Subject: Re: [RESEND PATCH v3 1/2] kho: add KHOSER_COPY_TYPE(UN)SAFE for phys copy
Date: Mon, 22 Jun 2026 22:59:04 +0000 [thread overview]
Message-ID: <9huzse6ew5af.fsf@tarunix.c.googlers.com> (raw)
In-Reply-To: <178215570871.91679.11260349768439750235.b4-review@b4>
Mike Rapoport <rppt@kernel.org> writes:
> On Mon, 22 Jun 2026 11:12:14 +0000, Tarun Sahu <tarunsahu@google.com> wrote:
>> diff --git a/include/linux/kho/abi/kexec_handover.h b/include/linux/kho/abi/kexec_handover.h
>> index 5e2eb8519bda..618408fbe9c9 100644
>> --- a/include/linux/kho/abi/kexec_handover.h
>> +++ b/include/linux/kho/abi/kexec_handover.h
>> @@ -139,6 +139,18 @@
>> (typeof((s).ptr))((s).phys ? phys_to_virt((s).phys) : NULL); \
>> })
>>
>> +/* Copies one serializable pointer to another of same type. */
>> +#define KHOSER_COPY_TYPESAFE(dest, src) \
>
> Maybe name if KHOSER_COPY_PTR?
>
>> + ({ \
>> + typecheck(typeof((dest).ptr), (src).ptr); \
>
> And if we could replace the typecheck with some other magic to allow
> void * we won't need the unsafe version.
Done! Sent V4.
Thanks for reviewing.
~Tarun
>
> --
> Sincerely yours,
> Mike.
next prev parent reply other threads:[~2026-06-22 22:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-22 11:12 [RESEND PATCH v3 0/2] luo: convert serialized ptr to KHOSER_PTR Tarun Sahu
2026-06-22 11:12 ` [RESEND PATCH v3 1/2] kho: add KHOSER_COPY_TYPE(UN)SAFE for phys copy Tarun Sahu
2026-06-22 19:15 ` Mike Rapoport
2026-06-22 22:59 ` tarunsahu [this message]
2026-06-22 11:12 ` [REESND PATCH v3 2/2] luo: Update serialized data to use KHOSER_PTR Tarun Sahu
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=9huzse6ew5af.fsf@tarunix.c.googlers.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox