From: Scott Wood <scottwood@freescale.com>
To: Kevin Hao <haokexin@gmail.com>
Cc: linuxppc <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/4] powerpc/book3e: introduce external_input_edge exception handler for 64bit kernel
Date: Mon, 13 May 2013 10:47:17 -0500 [thread overview]
Message-ID: <1368460037.8202.8@snotra> (raw)
In-Reply-To: <1368314784-971-2-git-send-email-haokexin@gmail.com> (from haokexin@gmail.com on Sat May 11 18:26:21 2013)
On 05/11/2013 06:26:21 PM, Kevin Hao wrote:
> In the external proxy facility mode, the interrupt is automatically
> acknowledged with the same effect as reading the IACK register. So
> this makes external input interrupt more like edge sensitive. That
> means we can leave the irq hard enabled when it occurs with irq soft
> disabled just like the dec and doorbell interrupt. But the External
> Proxy Register(EPR) is only considered valid from the time that the
> external interrupt occurs until MSR[EE] is set to 1. So we have to
> save the EPR before irq hard enabled.
Is it really worth it? Are you having a real-world problem with =20
profilability as things stand, that this resolves? We should already =20
be no worse off than non-external-proxy hardware...
-Scott=
next prev parent reply other threads:[~2013-05-13 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-11 23:26 [PATCH 0/4] enable the PACA_IRQ_EE_EDGE support for book3e Kevin Hao
2013-05-11 23:26 ` [PATCH 1/4] powerpc/book3e: introduce external_input_edge exception handler for 64bit kernel Kevin Hao
2013-05-13 15:47 ` Scott Wood [this message]
2013-05-14 2:03 ` Kevin Hao
2013-05-15 21:30 ` Scott Wood
2013-05-16 8:43 ` Kevin Hao
2013-05-11 23:26 ` [PATCH 2/4] powerpc: move the patch_exception to a common place Kevin Hao
2013-05-11 23:26 ` [PATCH 3/4] powerpc: use patch_exception to update the debug exception handler Kevin Hao
2013-05-11 23:26 ` [PATCH 4/4] powerpc/fsl-book3e: enable the external_input_edge " Kevin Hao
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=1368460037.8202.8@snotra \
--to=scottwood@freescale.com \
--cc=haokexin@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).