linux-kernel - Re: [RFC 0/4] dynamically allocate arch specific system vectors

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: <20080914154825.GA13513@elte.hu>
Date:	Sun, 14 Sep 2008 17:48:25 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Dean Nelson <dcn@....com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Alan Mayer <ajm@....com>, jeremy@...p.org,
	rusty@...tcorp.com.au, suresh.b.siddha@...el.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <Yinghai.lu@....com>
Subject: Re: [RFC 0/4] dynamically allocate arch specific system vectors


* Ingo Molnar <mingo@...e.hu> wrote:

> > There are two kernel modules, sgi-gru and sgi-xp (in drivers/misc), 
> > that each need two vectors. And there's the broadcast assist unit 
> > (BAU) that is involved in tlb shootdown on uv, which currently uses 
> > statically reserved vector 0xf8 (UV_BAU_MESSAGE -- see 
> > uv_bau_init()).
> 
> while i understand the UV_BAU_MESSAGE case (TLB flushes are special), 
> why does sgi-gru and sgi-xp need to go that deep? They are drivers, 
> they should be able to make use of an ordinary irq just like the other 
> 2000 drivers we have do.

... but all in one, i still like this concept as it's a nice clean-up. I 
just dont think it should be exposed to generic drivers, and i think it 
needs further fixes and cleanups. (see my previous mails)

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