On 09/12/2016 08:26 AM, Jan Beulich wrote:
On 09.09.16 at 18:32, wrote:
>> Would that sound reasonable - am I overlooking something? To some extent this
>> might also applicable to the general case, although platform timer is now
>> only
>> used for initial seeding so probably a non-visible
>>> On 09.09.16 at 18:32, wrote:
> Would that sound reasonable - am I overlooking something? To some extent this
> might also applicable to the general case, although platform timer is now only
> used for initial seeding so probably a non-visible issue.
Wouldn't it already help to simply make TSC
On 08/30/2016 01:31 PM, Jan Beulich wrote:
On 30.08.16 at 14:10, wrote:
>> What would be a preferred period - probably capping it to a
>> day/hour/minutes? Or
>> keeping the current calculated value? Maximum right now in current platform
>> timers
>> are few minutes depending on the HPET fr
>>> On 30.08.16 at 14:10, wrote:
> What would be a preferred period - probably capping it to a day/hour/minutes?
> Or
> keeping the current calculated value? Maximum right now in current platform
> timers
> are few minutes depending on the HPET frequency.
Ideally I would see you just use the ca
On 08/29/2016 10:41 AM, Jan Beulich wrote:
On 26.08.16 at 17:12, wrote:
>> On 08/25/2016 11:13 AM, Jan Beulich wrote:
>> On 24.08.16 at 14:43, wrote:
And use to initialize platform time solely for clocksource=tsc,
as opposed to initializing platform overflow timer, which would
>>> On 26.08.16 at 17:12, wrote:
> On 08/25/2016 11:13 AM, Jan Beulich wrote:
> On 24.08.16 at 14:43, wrote:
>>> And use to initialize platform time solely for clocksource=tsc,
>>> as opposed to initializing platform overflow timer, which would
>>> only fire in ~180 years (on 2.2 Ghz Broadwel
On 08/25/2016 11:13 AM, Jan Beulich wrote:
On 24.08.16 at 14:43, wrote:
>> And use to initialize platform time solely for clocksource=tsc,
>> as opposed to initializing platform overflow timer, which would
>> only fire in ~180 years (on 2.2 Ghz Broadwell processor).
>
> Do we really want to
>>> On 24.08.16 at 14:43, wrote:
> And use to initialize platform time solely for clocksource=tsc,
> as opposed to initializing platform overflow timer, which would
> only fire in ~180 years (on 2.2 Ghz Broadwell processor).
Do we really want to risk this time period going down by two orders
of m
And use to initialize platform time solely for clocksource=tsc,
as opposed to initializing platform overflow timer, which would
only fire in ~180 years (on 2.2 Ghz Broadwell processor).
Signed-off-by: Joao Martins
---
Cc: Jan Beulich
Cc: Andrew Cooper
Changes since v2:
- Remove pointless inti
