Why not use existing seqlock's?
-----Original Message-----
From: Thomas Gleixner [mailto:[email protected]]
Sent: Thursday, February 9, 2017 9:08 AM
To: Vitaly Kuznetsov <[email protected]>
Cc: [email protected]; Andy Lutomirski <[email protected]>; Ingo Molnar
<[email protected]>; H. Peter Anvin <[email protected]>; KY Srinivasan
<[email protected]>; Haiyang Zhang <[email protected]>; Stephen Hemminger
<[email protected]>; Dexuan Cui <[email protected]>;
[email protected]; [email protected];
[email protected]
Subject: Re: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method
On Thu, 9 Feb 2017, Vitaly Kuznetsov wrote:
> +#ifdef CONFIG_HYPERV_TSCPAGE
> +static notrace u64 vread_hvclock(int *mode) {
> + const struct ms_hyperv_tsc_page *tsc_pg =
> + (const struct ms_hyperv_tsc_page *)&hvclock_page;
> + u64 sequence, scale, offset, current_tick, cur_tsc;
> +
> + while (1) {
> + sequence = READ_ONCE(tsc_pg->tsc_sequence);
> + if (!sequence)
> + break;
> +
> + scale = READ_ONCE(tsc_pg->tsc_scale);
> + offset = READ_ONCE(tsc_pg->tsc_offset);
> + rdtscll(cur_tsc);
> +
> + current_tick = mul_u64_u64_shr(cur_tsc, scale, 64) + offset;
> +
> + if (READ_ONCE(tsc_pg->tsc_sequence) == sequence)
> + return current_tick;
That sequence stuff lacks still a sensible explanation. It's fundamentally
different from the sequence counting we do in the kernel, so documentation for
it is really required.
Thanks,
tglx
_______________________________________________
devel mailing list
[email protected]
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
