linux-kernel - Re: about cs5536 interrupt ack

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] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64N.0707161556560.15539@blysk.ds.pg.gda.pl>
Date:	Mon, 16 Jul 2007 16:11:45 +0100 (BST)
From:	"Maciej W. Rozycki" <macro@...ux-mips.org>
To:	Songmao Tian <tiansm@...ote.com>
cc:	LinuxBIOS Mailing List <linuxbios@...uxbios.org>,
	marc.jones@....com, linux-kernel@...r.kernel.org,
	linux-mips@...ux-mips.org
Subject: Re: about cs5536 interrupt ack

On Thu, 12 Jul 2007, Songmao Tian wrote:

> 8259 problem  seems to be done with the attached patch, IDE hung seems to be
> the dma setting problem.
> 
> Thanks all for your advise, comments. I have learned a lot. now I continue to
> trace down the IDE problem.

 I would still recommend you to investigate the option of making the 8259A 
cores "transparent" and using the mapper registers to dispatch interrupts 
directly -- it would make processing of interrupt requests considerably 
faster and less complicated.  Please note that ffs() is O(1) and actually 
some two or three machine instructions on MIPS architecture processors and 
the model used by the mapper is closer to the spirit of how MIPS 
processors do interrupt handling.  With such an approach it will also 
likely be easier to integrate your changes upstream, than it would for 
your changes to i8259.{c,h} needed for your unusual setup to work.

 Of course as an intermediate solution during development to make the 
whole thing work the complicated use of the 8259A cores may be justified.

  Maciej
-
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/