linux-kernel - RE: [PATCH 1/1] X86: Mark the Hyper-V clocksource as being continuous

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <A70AC0C1B7E7FD478A6BF19705461AA01109C1@IMBER.smb.curriegrad2004.ca>
Date:	Tue, 2 Dec 2014 16:14:05 -0800
From:	"Jeff Leung" <jleung@...networks.ca>
To:	"KY Srinivasan" <kys@...rosoft.com>, <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

> 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@...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/