>From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
>Sent: Thursday, November 10, 2016 12:34 PM
>>> give a correct result without a dmesg log ?
>> [root@192.168.8.2 /]$ [root@192.168.8.2 /]$ taskset 65536 time sleep 2
>> & taskset 131072 time sleep 3
>Thanks for providing the numbers.
>So
On 08/11/2016 09:30, Noam Camus wrote:
>> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
>> Sent: Tuesday, November 1, 2016 10:02 PM
> ...
>> Assuming cpu0 and cpu1 are sibling, does
>
>> taskset 0x1 time sleep 2 & taskset 0x2 time sleep 3
>
> I will use 16,17 instead of 0,1
>> give a c
> From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> Sent: Tuesday, November 1, 2016 10:02 PM
...
>Assuming cpu0 and cpu1 are sibling, does
>taskset 0x1 time sleep 2 & taskset 0x2 time sleep 3
I will use 16,17 instead of 0,1
>give a correct result without a dmesg log ?
[root@192.168.8.2 /
On Mon, Oct 31, 2016 at 05:03:40PM +, Noam Camus wrote:
> >From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
> >Sent: Monday, October 31, 2016 12:53 PM
>
> >>
> >> The design idea is that for each core there is dedicated regirtser
>
> >s/regirtser/register/
>
> >Hey ! re-read yoursel
>From: Daniel Lezcano [mailto:daniel.lezc...@linaro.org]
>Sent: Monday, October 31, 2016 12:53 PM
>>
>> The design idea is that for each core there is dedicated regirtser
>s/regirtser/register/
>Hey ! re-read yourself.
Thanks, I do but sometimes reading over and over and still left with such t
Hi Daniel,
On 10/31/2016 10:03 AM, Noam Camus wrote:
>> Oops, wait. Here, arch/arc/kernel/time.c should be moved in
>> drivers/clocksource and consolidated with this driver.
>> >Very likely, CPUHP_AP_ARC_TIMER_STARTING can be used for all ARC timers.
> Indeed the ARC timer driver served as my ins
On Sun, Oct 23, 2016 at 03:12:28PM +0300, Noam Camus wrote:
> From: Noam Camus
>
> Till now we used clockevent from generic ARC driver.
> This was enough as long as we worked with simple multicore SoC.
> When we are working with multithread SoC each HW thread can be
> scheduled to receive timer i
On Sun, Oct 23, 2016 at 03:12:28PM +0300, Noam Camus wrote:
> From: Noam Camus
>
> Till now we used clockevent from generic ARC driver.
> This was enough as long as we worked with simple multicore SoC.
> When we are working with multithread SoC each HW thread can be
> scheduled to receive timer i
8 matches
Mail list logo
