linux-kernel - Re: Is it possible to change IRQ for certain device?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <75b66ecd0801132204r5d4a5401hacc1de871342cf8c@mail.gmail.com>
Date:	Mon, 14 Jan 2008 01:04:19 -0500
From:	"Lee Revell" <rlrevell@...-job.com>
To:	"Bryan Donlan" <bdonlan@...il.com>
Cc:	"Jan Marek" <linux@...ard.jcu.cz>,
	"linux-os (Dick Johnson)" <linux-os@...logic.com>,
	lkml <linux-kernel@...r.kernel.org>
Subject: Re: Is it possible to change IRQ for certain device?

On Jan 14, 2008 12:30 AM, Bryan Donlan <bdonlan@...il.com> wrote:
>
> On Jan 13, 2008 10:57 PM, Lee Revell <rlrevell@...-job.com> wrote:
> > On Jan 11, 2008 11:57 AM, Jan Marek <linux@...ard.jcu.cz> wrote:
> > Why is a shared IRQ a problem for you?  IRQ handlers are supposed to
> > be fast enough that disabling an IRQ line for the duration of the
> > handler execution should not be a problem even if the IRQ is shared.
> > VGA interrupts in particular should only fire once per frame and only
> > need to flip some bits to wake up any processes waiting on vsync.
> >
> > If you have issues with a shared VGA interrupt then the bug is that
> > some IRQ handler runs for too long and should be deferring work to a
> > bottom half.
>
> Jan is apparently using the nvidia binary driver, so I doubt it will
> be possible to fix the bug that prevents it from sharing IRQs.
>

Ah, of course, stupid me.  Thought I was on linux-audio-user where
this is a FAQ (for completely different reasons) and not LKML.

But this is strange - I'm sure I've seen people using that driver with
a shared IRQ before.

Jan, maybe you can blacklist ohci-hcd as a workaround?  In any case
let's take this discussion off LKML so as not to spam the list with
binary only driver issues.

Lee
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/