> We have had the Hyper-V clocksource for sometime now and this patch just marks this > clocksource as being continuous. Nothing has changed with regards to timesynch. Alright, that cleared up that question. Gleaning around from the source tree, I don't seem to comprehend what changes are being made when the clock source has the flag CLOCK_SOURCE_IS_CONTINUOUS marked. > Regards, > > K. Y > > > > > > -----Original Message----- > > > From: linux-kernel-owner@xxxxxxxxxxxxxxx > > [mailto:linux-kernel-owner@xxxxxxxxxxxxxxx] > > > On Behalf Of K. Y. Srinivasan > > > Sent: Tuesday, December 2, 2014 17:04 > > > To: x86@xxxxxxxxxx; gregkh@xxxxxxxxxxxxxxxxxxx; > > linux-kernel@xxxxxxxxxxxxxxx; > > > devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx; > > > jasowang@xxxxxxxxxx; tglx@xxxxxxxxxxxxx; hpa@xxxxxxxxx > > > Cc: K. Y. Srinivasan; stable@xxxxxxxxxxxxxxx > > > Subject: [PATCH 1/1] X86: Mark the Hyper-V clocksource as being > > continuous > > > > > > The clocksource based on Hyper-V per-partition reference count MSR > > > is > > continuous. Mark > > > it accordingly. > > > > > > Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx> > > > cc: stable@xxxxxxxxxxxxxxx > > > --- > > > arch/x86/kernel/cpu/mshyperv.c | 1 + > > > 1 files changed, 1 insertions(+), 0 deletions(-) > > > > > > diff --git a/arch/x86/kernel/cpu/mshyperv.c > > b/arch/x86/kernel/cpu/mshyperv.c index > > > a450373..939155f 100644 > > > --- a/arch/x86/kernel/cpu/mshyperv.c > > > +++ b/arch/x86/kernel/cpu/mshyperv.c > > > @@ -107,6 +107,7 @@ static struct clocksource hyperv_cs = { > > > .rating = 400, /* use this when running on Hyperv*/ > > > .read = read_hv_clock, > > > .mask = CLOCKSOURCE_MASK(64), > > > + .flags = CLOCK_SOURCE_IS_CONTINUOUS, > > > }; > > > > > > static void __init ms_hyperv_init_platform(void) > > > -- > > > 1.7.4.1 > > > > > > -- > > > To unsubscribe from this list: send the line "unsubscribe > > linux-kernel" in the body of a > > > message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > > > http://vger.kernel.org/majordomo-info.html > > > Please read the FAQ at http://www.tux.org/lkml/ > _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
