hi,
> hi,
>
> On 02/21/2012 08:11 AM, YAMAMOTO Takashi wrote:
>> hi,
>>
>>> On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
>>>> hi,
>>>>
>>>>> Hi,
>>>>>
>>>>> I would like to change upree
hi,
On 02/21/2012 08:11 AM, YAMAMOTO Takashi wrote:
> hi,
>
>> On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
>>> hi,
>>>
>>>> Hi,
>>>>
>>>> I would like to change upreempt_pri to default to 0 as this
>>>> makes w
hi,
> On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
>> hi,
>>
>>> Hi,
>>>
>>> I would like to change upreempt_pri to default to 0 as this makes
>>> wakeups where the interrupted cpu schedules a thread on another
>>> cpu
On 01/10/2012 03:30 AM, YAMAMOTO Takashi wrote:
> hi,
>
>> Hi,
>>
>> I would like to change upreempt_pri to default to 0 as this makes
>> wakeups where the interrupted cpu schedules a thread on another
>> cpu behave like as if it where scheduled on the inter
hi,
> Hi,
>
> I would like to change upreempt_pri to default to 0 as this makes
> wakeups where the interrupted cpu schedules a thread on another cpu
> behave like as if it where scheduled on the interrupted cpu.
>
> For the case that the to be scheduled on cpu is the in
On 01/07/2012 12:55 PM, David Laight wrote:
On Thu, Jan 05, 2012 at 11:19:54PM +0100, Lars Heidieker wrote:
Hi,
I would like to change upreempt_pri to default to 0 as this makes
wakeups where the interrupted cpu schedules a thread on another cpu
behave like as if it where scheduled on the
On Thu, Jan 05, 2012 at 11:19:54PM +0100, Lars Heidieker wrote:
> Hi,
>
> I would like to change upreempt_pri to default to 0 as this makes
> wakeups where the interrupted cpu schedules a thread on another cpu
> behave like as if it where scheduled on the interrupted cpu.
Are yo
Hi,
I would like to change upreempt_pri to default to 0 as this makes
wakeups where the interrupted cpu schedules a thread on another cpu
behave like as if it where scheduled on the interrupted cpu.
For the case that the to be scheduled on cpu is the interrupted one,
the behavior is like
