From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stuart Yoder <b08248@gmail.com>
Cc: Laurentiu Tudor <Laurentiu.Tudor@freescale.com>,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/booke64: Configurable lazy interrupt disabling
Date: Sat, 21 Jan 2012 10:05:55 +1100 [thread overview]
Message-ID: <1327100755.2923.6.camel@pasglop> (raw)
In-Reply-To: <CALRxmdA9mh6x5YGK1oFHvgmV-RsnN6WkxhpZbcRJv1S8Y0RH1w@mail.gmail.com>
On Thu, 2012-01-19 at 13:29 -0600, Stuart Yoder wrote:
> Also, Scott had posted an approach to do option #2 a while back,
> but as I recall there was some negative feedback about this. See:
> <http://lists.ozlabs.org/pipermail/linuxppc-dev/2011-August/092103.html>
I see... the problems with doorbells are workable tho. A reject hcall
could also raise the CPU priority to avoid lower priority interrupts for
example. The decrementer option works too.
Another approach is to do an hcall into the interrupt re-enable path
when an interrupt occurred while masked, which is what we do on i or
ps3, which could then trigger a replay.
Traditionally EE's have always been "level sensitive" on PowerPC, the
way you changed that is arguably an utterly broken HW design and I am
not too keen on changing our core interrupt handling to deal with it via
ifdef's if we can find a less invasive solution.
Cheers,
Ben.
next prev parent reply other threads:[~2012-01-20 23:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 14:35 [PATCH] powerpc/booke64: Configurable lazy interrupt disabling Laurentiu Tudor
2012-01-18 21:10 ` Benjamin Herrenschmidt
2012-01-19 13:18 ` Tudor Laurentiu
2012-01-19 19:21 ` Stuart Yoder
2012-01-19 19:29 ` Stuart Yoder
2012-01-20 23:05 ` Benjamin Herrenschmidt [this message]
2012-01-23 19:21 ` Scott Wood
2012-01-23 20:50 ` Benjamin Herrenschmidt
2012-01-25 14:32 ` Tudor Laurentiu
2012-01-30 21:47 ` Scott Wood
2012-01-30 22:15 ` Benjamin Herrenschmidt
2012-01-30 23:13 ` Scott Wood
2012-01-20 23:02 ` Benjamin Herrenschmidt
2012-01-23 19:31 ` Scott Wood
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=1327100755.2923.6.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Laurentiu.Tudor@freescale.com \
--cc=b08248@gmail.com \
--cc=linuxppc-dev@lists.ozlabs.org \
/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).