[patch] Re: proposal: stop using the xen_system_time timecounter in dom0

["Mathew, Cherry G." <c%bow.st@localhost>]

>>>>> On Sun, 23 Jun 2024 08:05:13 +0000, "Mathew, Cherry G." <c%bow.st@localhost> said:

[...]

> +       return _hypercall2(int, sched_op, SCHEDOP_pin_override, SHUTDOWN_suspend);
                                                                  ^^^^^^^^^^^^^^^^

Sorry, that would not have the desired effect even if it had compiled,
but you get the idea. Pasting (hopefully) an updated one for the desired
outcome - YKWIM.

--- a/sys/arch/xen/xen/xen_clock.c      Sun Jun 23 00:53:48 2024 +0000
+++ b/sys/arch/xen/xen/xen_clock.c      Sun Jun 23 08:10:36 2024 +0000
@@ -929,6 +929,17 @@
        xen_resumeclocks(ci);

 #ifdef DOM0OPS
+#if __XEN_INTERFACE_VERSION__ >= 0x00030201
+
+       struct sched_pin_override = {
+               .pcpu = curcpu()->ci_cpuid,
+       };
+
+       return _hypercall2(int, sched_op, SCHEDOP_pin_override, &shutdown_pin_override);
+#else
+       return _hypercall2(int, sched_op, SCHEDOP_pin_override, curcpu()->ci_cpuid);
+#endif
+
        /*
         * If this is a privileged dom0, start pushing the wall
         * clock time back to the Xen hypervisor.

-- 
Math/(~cherry)