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]

Date:	Thu, 18 Sep 2008 12:18:11 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Dean Nelson <dcn@....com>
CC:	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Ingo Molnar <mingo@...e.hu>, Alan Mayer <ajm@....com>,
	Dimitri Sivanich <sivanich@....com>, jeremy@...p.org,
	rusty@...tcorp.com.au, suresh.b.siddha@...el.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <Yinghai.lu@....com>
Subject: Re: [RFC 0/4] dynamically allocate arch specific system vectors

Dean Nelson wrote:
> On Wed, Sep 17, 2008 at 11:59:05AM -0700, Eric W. Biederman wrote:
>> I need to look at these patches some more (apologies I got busy).
> 
> Thanks for taking a look.
> 
> I've got a not-quite-complete new version of the patchset that addresses
> most of the issues raised by Ingo. At it's heart is the following:
> 

What would seem most intuitive to me would have been, in this case, to
add this as a new MSI IRQ chip type.  We already have several of those
(PCI vs HT), and this *should* give you all the hooks you need.

	-hpa

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