|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] [PATCH 4/6] xen/hypercall: Cope with -ERESTART on more hypercall paths
Hi Andrew, On 05/12/2019 22:30, Andrew Cooper wrote: It is not entirely trivial to me that KEXEC_REBOOT refers to KEXEC_DEFAULT_TYPE. The more that if you look at the kexec_reboot() helper, it will not return (see BUG()). What may return is continue_hypercall_on_cpu(). So would it make sense to use KEXEC_DEFAULT_TYPE? [...]
Shall we indent create_continuation the same way as out? [...] Shouldn't it be long (or unsigned long) here? Otherwise, the return of hypercall_create_continuation() may be truncated.@@ -1263,13 +1263,25 @@ static int do_kexec_op_internal(unsigned long op,long do_kexec_op(unsigned long op, XEN_GUEST_HANDLE_PARAM(void) uarg) + + if ( ret == -ERESTART ) + ret = hypercall_create_continuation(__HYPERVISOR_kexec_op, + "lh", op, uarg); + + return ret; } [...]
Similar question as the previous label create_continuation. -- Julien Grall _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |