Wolfgang Mauerer wrote:
> diff --git a/arch/x86/kernel/vsyscall_64.c b/arch/x86/kernel/vsyscall_64.c
> index 8cb4974..f1b90f7 100644
> --- a/arch/x86/kernel/vsyscall_64.c
> +++ b/arch/x86/kernel/vsyscall_64.c
> @@ -32,6 +32,7 @@
> #include <linux/cpu.h>
> #include <linux/smp.h>
> #include <linux/notifier.h>
> +#include <linux/ipipe_tickdev.h>
>
> #include <asm/vsyscall.h>
> #include <asm/pgtable.h>
> @@ -89,6 +90,11 @@ void update_vsyscall(struct timespec *wall_time, struct
> clocksource *clock)
> vsyscall_gtod_data.wall_to_monotonic = wall_to_monotonic;
> vsyscall_gtod_data.wall_time_coarse = __current_kernel_time();
> write_sequnlock_irqrestore(&vsyscall_gtod_data.lock, flags);
> +
> +#ifdef CONFIG_IPIPE_HOSTRT
> + if (clock == &clocksource_tsc)
> + update_ipipe_hostrt(wall_time, clock);
> +#endif
The idea was to use ipipe_dispatch_event here, and implement the event
handler in Xenomai. I wonder, however, if we should not do this at the
call sites ov update_vsyscall, or wrap update_vsyscall, so that we can
modify only architecture-independent code.
--
Gilles.
_______________________________________________
Adeos-main mailing list
[email protected]
https://mail.gna.org/listinfo/adeos-main
