>
>
> Out of curiosity,
>
> shouldn't we rather try to make set_memory_decrypted() more atomic to avoid
> the need to hunt down all users of the API? E.g. in Hyper-V's
> __vmbus_establish_gpadl() I see:
>
> ret = set_memory_decrypted((unsigned long)kbuffer,
> PFN_UP(size));
> if (ret) {
> dev_warn(&channel->device_obj->device,
> ...
>
> doesn't it have the exact same issue you're trying to address for kvmclock?
>
This patch should show the reason
https://lkml.org/lkml/2023/10/24/1369
thanks
-Li
