From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <vbarshak@ru.mvista.com>
Received: from buildserver.ru.mvista.com (unknown [213.79.90.228])
	by ozlabs.org (Postfix) with ESMTP id 88B711007E3
	for <linuxppc-dev@ozlabs.org>; Thu, 29 Oct 2009 08:50:31 +1100 (EST)
Message-ID: <4AE8B761.3090902@ru.mvista.com>
Date: Thu, 29 Oct 2009 00:28:01 +0300
From: Valentine <vbarshak@ru.mvista.com>
MIME-Version: 1.0
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: [PATCH v3] powerpc/ppc64: Use preempt_schedule_irq instead of
	preempt_schedule
References: <20091019182858.GA10495@ru.mvista.com>	
	<1256601324.2076.49.camel@pasglop>
	<1256622077.11607.85.camel@pasglop>	
	<4AE89936.6080803@ru.mvista.com> <1256761844.26770.2.camel@pasglop>
In-Reply-To: <1256761844.26770.2.camel@pasglop>
Content-Type: text/plain; charset=UTF-8; format=flowed
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org, paulus@samba.org
List-Id: Linux on PowerPC Developers Mail List <linuxppc-dev.lists.ozlabs.org>
List-Unsubscribe: <https://lists.ozlabs.org/options/linuxppc-dev>,
	<mailto:linuxppc-dev-request@lists.ozlabs.org?subject=unsubscribe>
List-Archive: <http://lists.ozlabs.org/pipermail/linuxppc-dev>
List-Post: <mailto:linuxppc-dev@lists.ozlabs.org>
List-Help: <mailto:linuxppc-dev-request@lists.ozlabs.org?subject=help>
List-Subscribe: <https://lists.ozlabs.org/listinfo/linuxppc-dev>,
	<mailto:linuxppc-dev-request@lists.ozlabs.org?subject=subscribe>

Benjamin Herrenschmidt wrote:
> On Wed, 2009-10-28 at 22:19 +0300, Valentine wrote:
> 
>> I'm just not sure that we need to clear HARDIRQEN here, since we don't 
>> really hard-disable the the interrupts.
> 
> We do, or rather, we come in with the interrupts hard disabled, no ?

Yes, looks like the interrupts are disabled at this point (before 
preempt_schedule_irq) most of the times, but we don't hard-disable them 
here. We just soft-disable them to make preempt_schedule_irq happy. Even 
if an interrupt fires, it will be hard-disabled and the hardirq flag 
will be cleared by the exception handler right away. I just think that 
there's no need to clear hardirq flag if we don't clear MSR_EE.

Thanks,
Val.
> 
> Ben.
> 
>> Thanks,
>> Val.
>>
>>> +	TRACE_DISABLE_INTS
>>> +
>>> +	/* Call the scheduler with soft IRQs off */
>>> +1:	bl	.preempt_schedule_irq
>>> +
>>> +	/* Hard-disable interrupts again (and update PACA) */
>>>  #ifdef CONFIG_PPC_BOOK3E
>>> -	wrteei	1
>>> -	bl	.preempt_schedule
>>>  	wrteei	0
>>>  #else
>>> -	ori	r10,r10,MSR_EE
>>> -	mtmsrd	r10,1		/* reenable interrupts */
>>> -	bl	.preempt_schedule
>>>  	mfmsr	r10
>>> -	clrrdi	r9,r1,THREAD_SHIFT
>>> -	rldicl	r10,r10,48,1	/* disable interrupts again */
>>> +	rldicl	r10,r10,48,1
>>>  	rotldi	r10,r10,16
>>>  	mtmsrd	r10,1
>>>  #endif /* CONFIG_PPC_BOOK3E */
>>> +	li	r0,0
>>> +	stb	r0,PACAHARDIRQEN(r13)
>>> +
>>> +	/* Re-test flags and eventually loop */
>>> +	clrrdi	r9,r1,THREAD_SHIFT
>>>  	ld	r4,TI_FLAGS(r9)
>>>  	andi.	r0,r4,_TIF_NEED_RESCHED
>>>  	bne	1b
>>>  	b	restore
>>>  
>>>  user_work:
>>> -#endif
>>> +#endif /* CONFIG_PREEMPT */
>>> +
>>>  	/* Enable interrupts */
>>>  #ifdef CONFIG_PPC_BOOK3E
>>>  	wrteei	1
> 
>