[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BY2PR0301MB0711D77DC4E020F9824BC9D7A07B0@BY2PR0301MB0711.namprd03.prod.outlook.com>
Date: Wed, 3 Dec 2014 00:06:46 +0000
From: KY Srinivasan <kys@...rosoft.com>
To: Jeff Leung <jleung@...networks.ca>,
"x86@...nel.org" <x86@...nel.org>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"devel@...uxdriverproject.org" <devel@...uxdriverproject.org>,
"olaf@...fle.de" <olaf@...fle.de>,
"apw@...onical.com" <apw@...onical.com>,
"jasowang@...hat.com" <jasowang@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"hpa@...or.com" <hpa@...or.com>
CC: "stable@...r.kernel.org" <stable@...r.kernel.org>
Subject: RE: [PATCH 1/1] X86: Mark the Hyper-V clocksource as being continuous
> -----Original Message-----
> From: Jeff Leung [mailto:jleung@...networks.ca]
> Sent: Tuesday, December 2, 2014 3:58 PM
> To: KY Srinivasan; x86@...nel.org; gregkh@...uxfoundation.org; linux-
> kernel@...r.kernel.org; devel@...uxdriverproject.org; olaf@...fle.de;
> apw@...onical.com; jasowang@...hat.com; tglx@...utronix.de;
> hpa@...or.com
> Cc: stable@...r.kernel.org
> Subject: RE: [PATCH 1/1] X86: Mark the Hyper-V clocksource as being
> continuous
>
> Does this mean that host-to guest timesync now works properly with Linux
> guests?
>
> -- Jeff
Jeff,
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.
Regards,
K. Y
>
> > -----Original Message-----
> > From: linux-kernel-owner@...r.kernel.org
> [mailto:linux-kernel-owner@...r.kernel.org]
> > On Behalf Of K. Y. Srinivasan
> > Sent: Tuesday, December 2, 2014 17:04
> > To: x86@...nel.org; gregkh@...uxfoundation.org;
> linux-kernel@...r.kernel.org;
> > devel@...uxdriverproject.org; olaf@...fle.de; apw@...onical.com;
> > jasowang@...hat.com; tglx@...utronix.de; hpa@...or.com
> > Cc: K. Y. Srinivasan; stable@...r.kernel.org
> > 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@...rosoft.com>
> > cc: stable@...r.kernel.org
> > ---
> > 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@...r.kernel.org More majordomo info at
> > http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists