>>> On 23.03.16 at 13:05, wrote:
> On 03/23/2016 07:28 AM, Jan Beulich wrote:
>> Sure - it seems quite obvious that all boot time available CPUs
>> should be checked.
> Cool, so I will go with moving init_xen_time right after all CPUs are up but
> before initcalls are invoked.
I think your other
On 03/23/2016 07:28 AM, Jan Beulich wrote:
On 22.03.16 at 21:40, wrote:
>> On 03/22/2016 04:02 PM, Jan Beulich wrote:
>> On 22.03.16 at 16:51, wrote:
On 03/22/2016 12:46 PM, Jan Beulich wrote:
On 22.03.16 at 13:41, wrote:
>>>
>> I found out one issue in the tsc c
>>> On 22.03.16 at 21:40, wrote:
> On 03/22/2016 04:02 PM, Jan Beulich wrote:
> On 22.03.16 at 16:51, wrote:
>>> On 03/22/2016 12:46 PM, Jan Beulich wrote:
>>> On 22.03.16 at 13:41, wrote:
>>
> I found out one issue in the tsc clocksource initialization path with
> respect t
On 03/22/2016 04:02 PM, Jan Beulich wrote:
On 22.03.16 at 16:51, wrote:
>
>>
>> On 03/22/2016 12:46 PM, Jan Beulich wrote:
>> On 22.03.16 at 13:41, wrote:
>>>
On 03/18/2016 08:21 PM, Andrew Cooper wrote:
> On 17/03/16 16:12, Joao Martins wrote:
>> Introduce support f
>>> On 22.03.16 at 16:51, wrote:
>
> On 03/22/2016 12:46 PM, Jan Beulich wrote:
> On 22.03.16 at 13:41, wrote:
>>
>>>
>>> On 03/18/2016 08:21 PM, Andrew Cooper wrote:
On 17/03/16 16:12, Joao Martins wrote:
> Introduce support for using TSC as platform time which is the highest
>>>
On 03/22/2016 12:46 PM, Jan Beulich wrote:
On 22.03.16 at 13:41, wrote:
>
>>
>> On 03/18/2016 08:21 PM, Andrew Cooper wrote:
>>> On 17/03/16 16:12, Joao Martins wrote:
Introduce support for using TSC as platform time which is the highest
resolution time and most performant to get
>>> On 22.03.16 at 13:41, wrote:
>
> On 03/18/2016 08:21 PM, Andrew Cooper wrote:
>> On 17/03/16 16:12, Joao Martins wrote:
>>> Introduce support for using TSC as platform time which is the highest
>>> resolution time and most performant to get (~20 nsecs). Though there
>>> are also several pro
On 03/18/2016 08:21 PM, Andrew Cooper wrote:
> On 17/03/16 16:12, Joao Martins wrote:
>> Introduce support for using TSC as platform time which is the highest
>> resolution time and most performant to get (~20 nsecs). Though there
>> are also several problems associated with its usage, and there
On 03/18/2016 08:21 PM, Andrew Cooper wrote:
> On 17/03/16 16:12, Joao Martins wrote:
>> Introduce support for using TSC as platform time which is the highest
>> resolution time and most performant to get (~20 nsecs). Though there
>> are also several problems associated with its usage, and there
On 17/03/16 16:12, Joao Martins wrote:
> Introduce support for using TSC as platform time which is the highest
> resolution time and most performant to get (~20 nsecs). Though there
> are also several problems associated with its usage, and there isn't a
> complete (and architecturally defined) gu
10 matches
Mail list logo
