linux-kernel - Re: [PATCH 0/5] Message signaled irq handling cleanups

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]

Date:	Wed, 27 Sep 2006 14:29:33 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andrew Morton <akpm@...l.org>
Cc:	<linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	"Luck, Tony" <tony.luck@...el.com>, Andi Kleen <ak@...e.de>,
	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Subject: Re: [PATCH 0/5] Message signaled irq handling cleanups

ebiederm@...ssion.com (Eric W. Biederman) writes:

> The following patch set should be enough to clear up the
> outstanding issues with genirq on i386 and x86_64.  This actually
> takes things a step farther and moves all of architecture
> dependencies I could find into the appropriate architecture.
>
> So hopefully we are finally close enough that other architectures
> will be able implement msi support, without too much trouble.
>
> msi: Simplify msi sanity checks by adding with generic irq code.
> msi: Only use a single irq_chip for msi interrupts
> msi: Refactor and move the msi irq_chip into the arch code.
> msi: Move the ia64 code into arch/ia64
> htirq: Tidy up the htirq code
>
> Eric

Grr.. My ia64 compiler is way too slow.  It just told me I had some
trivial bugs in the altix portion of what I posted.   Sorry I forgot
to mention all I can do is compile test ia64.

So here comes a second time with code that actually compiles :)

Darn this code that is so ugly that you have to test the cleanup on
multiple architectures!

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