From: Scott Wood <scottwood@freescale.com>
To: Rune Torgersen <runet@innovsys.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: Oops with PREEMPT-RT on 2.6.25.4
Date: Mon, 19 May 2008 16:49:43 -0500 [thread overview]
Message-ID: <4831F5F7.9050900@freescale.com> (raw)
In-Reply-To: <DCEAAC0833DD314AB0B58112AD99B93B04690276@ismail.innsys.innovsys.com>
Rune Torgersen wrote:
> Scott Wood wrote:
>> Try calling irq_set_chip_and_handler() with handle_level_irq, rather
>> than irq_set_chip(). The -rt patch doesn't seem to have threadified
>> the __do_IRQ() path.
>
> The demuxer is setting itself up with set_irq_chained handler(), any
> pointers on how to change to irq_set_chip_and_handler()?
No, I mean the call to set_irq_chip() in pci_pic_host_map() where it
sets up the IRQs it manages, not the cascade IRQ itself.
-Scott
next prev parent reply other threads:[~2008-05-19 21:49 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 19:05 Oops with PREEMPT-RT on 2.6.25.4 Rune Torgersen
2008-05-19 19:05 ` Rune Torgersen
2008-05-19 19:05 ` Rune Torgersen
2008-05-19 19:29 ` Scott Wood
2008-05-19 19:29 ` Scott Wood
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:41 ` Rune Torgersen
2008-05-19 19:58 ` Gregory Haskins
2008-05-19 19:58 ` Gregory Haskins
2008-05-19 21:11 ` Scott Wood
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:16 ` Rune Torgersen
2008-05-19 21:38 ` Scott Wood
2008-05-19 21:46 ` Rune Torgersen
2008-05-19 21:46 ` Rune Torgersen
2008-05-19 21:49 ` Scott Wood [this message]
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:08 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
2008-05-19 22:23 ` Rune Torgersen
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=4831F5F7.9050900@freescale.com \
--to=scottwood@freescale.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=runet@innovsys.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 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.