[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150814063250.GB18603@localhost.localdomain>
Date: Fri, 14 Aug 2015 08:32:51 +0200
From: Richard Cochran <richardcochran@...il.com>
To: "Hall, Christopher S" <christopher.s.hall@...el.com>
Cc: "john.stultz@...aro.org" <john.stultz@...aro.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@...el.com>,
"Ronciak, John" <john.ronciak@...el.com>,
"hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH v2 4/4] Added getsynctime64() callback
On Thu, Aug 13, 2015 at 09:10:36PM +0000, Hall, Christopher S wrote:
> > > + if (!cpu_has_art)
> > > + return -EOPNOTSUPP;
> >
> > Perform this check before registration, setting .getsynctime64
> > accordingly.
>
> The problem here is that ART initialization doesn't happen until we
> install TSC as a clocksource. This design is per Thomas'
> suggestion. That occurs after the driver is loaded (as a module).
So that 'cpu_has_art' actually means 'cpu_has_art_and_has_been_initialized'?
In any case, returning EOPNOTSUPP early on, but OK later seems mean to
me. If the clocks aren't ready yet, the error should be EBUSY so that
user space knows it can try again.
Thanks,
Richard
--
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