From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Valentine <vbarshak@ru.mvista.com>
Cc: olof@lixom.net, linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH v3] powerpc/ppc64: Use preempt_schedule_irq instead of preempt_schedule
Date: Thu, 29 Oct 2009 07:30:44 +1100 [thread overview]
Message-ID: <1256761844.26770.2.camel@pasglop> (raw)
In-Reply-To: <4AE89936.6080803@ru.mvista.com>
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 ?
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
next prev parent reply other threads:[~2009-10-28 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-19 18:28 [PATCH] [RFC] PowerPC64: Use preempt_schedule_irq instead of preempt_schedule when returning from exceptions Valentine Barshak
2009-10-26 23:55 ` Benjamin Herrenschmidt
2009-10-27 5:41 ` [PATCH v3] powerpc/ppc64: Use preempt_schedule_irq instead of preempt_schedule Benjamin Herrenschmidt
2009-10-28 19:19 ` Valentine
2009-10-28 20:30 ` Benjamin Herrenschmidt [this message]
2009-10-28 21:28 ` Valentine
2009-10-28 21:37 ` Benjamin Herrenschmidt
2009-10-28 22:49 ` Valentine
2009-10-29 0:49 ` Benjamin Herrenschmidt
2009-11-06 22:38 ` Valentine
2009-11-06 22:49 ` Benjamin Herrenschmidt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1256761844.26770.2.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=paulus@samba.org \
--cc=vbarshak@ru.mvista.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).