From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linuxppc-dev@ozlabs.org
Cc: Daniel Walker <dwalker@mvista.com>, Ingo Molnar <mingo@elte.hu>,
tglx@linutronix.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH -rt] powerpc update
Date: Sat, 28 Oct 2006 19:33:42 +0400 [thread overview]
Message-ID: <45437856.5060509@ru.mvista.com> (raw)
In-Reply-To: <454371AC.4030902@ru.mvista.com>
Hello, I wrote:
> 3. Do the same as x86 APIC driver does and use level/egde flows instead
> of fasteoi for the case when IRQs are threaded -- that ensues doing (2)
> as well.
Note that OpenPIC (as far as I could understand its h/w) is essentially
the same as IOAPIC/LAPIC couple on x86, i.e. a level-triggered IRQ remains
effectively globally masked until CPU writes to its local EOI reg. However,
the repetitive edge-triggered IRQ from the same line may still be detected
while being serviced on a CPU (hm, the questions is, can it be sent to any
other CPU in system while being handled on a certain CPU?)...
I hope somebody corrects me if I'm wrong about both x86 and PPC. :-)
>> Ingo
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: linuxppc-dev@ozlabs.org
Cc: Ingo Molnar <mingo@elte.hu>, Daniel Walker <dwalker@mvista.com>,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
mgreer@mvista.com
Subject: Re: [PATCH -rt] powerpc update
Date: Sat, 28 Oct 2006 19:33:42 +0400 [thread overview]
Message-ID: <45437856.5060509@ru.mvista.com> (raw)
In-Reply-To: <454371AC.4030902@ru.mvista.com>
Hello, I wrote:
> 3. Do the same as x86 APIC driver does and use level/egde flows instead
> of fasteoi for the case when IRQs are threaded -- that ensues doing (2)
> as well.
Note that OpenPIC (as far as I could understand its h/w) is essentially
the same as IOAPIC/LAPIC couple on x86, i.e. a level-triggered IRQ remains
effectively globally masked until CPU writes to its local EOI reg. However,
the repetitive edge-triggered IRQ from the same line may still be detected
while being serviced on a CPU (hm, the questions is, can it be sent to any
other CPU in system while being handled on a certain CPU?)...
I hope somebody corrects me if I'm wrong about both x86 and PPC. :-)
>> Ingo
WBR, Sergei
next prev parent reply other threads:[~2006-10-28 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-03 15:53 [PATCH -rt] powerpc update Daniel Walker
2006-10-03 15:53 ` Daniel Walker
2006-10-18 7:28 ` Ingo Molnar
2006-10-18 7:28 ` Ingo Molnar
2006-10-18 7:32 ` Ingo Molnar
2006-10-18 7:32 ` Ingo Molnar
2006-10-18 14:32 ` Daniel Walker
2006-10-18 14:32 ` Daniel Walker
2006-10-18 14:32 ` Ingo Molnar
2006-10-18 14:32 ` Ingo Molnar
2006-10-18 14:33 ` Ingo Molnar
2006-10-18 14:33 ` Ingo Molnar
2006-10-18 14:52 ` Daniel Walker
2006-10-18 14:52 ` Daniel Walker
2006-10-18 20:54 ` Daniel Walker
2006-10-18 20:54 ` Daniel Walker
2006-10-28 15:05 ` Sergei Shtylyov
2006-10-28 15:05 ` Sergei Shtylyov
2006-10-28 15:33 ` Sergei Shtylyov [this message]
2006-10-28 15:33 ` Sergei Shtylyov
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=45437856.5060509@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=dwalker@mvista.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.