linux-kernel - Re: [PATCH] x86_64: (NEW) 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:	Mon, 11 Aug 2008 18:59:30 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Mayer <ajm@....com>
Cc:	"Eric W. Biederman" <ebiederm@...ssion.com>, jeremy@...p.org,
	rusty@...tcorp.com.au, suresh.b.siddha@...el.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	Dean Nelson <dcn@....com>, Cliff Wickman <cpw@....com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH] x86_64:  (NEW) Dynamically allocate arch specific
	system vectors


* Alan Mayer <ajm@....com> wrote:

> Subject: [PATCH] x86_64: (NEW) Dynamically allocate arch specific 
> system vectors
>
> From: Alan Mayer <ajm@....com>
>
> On some systems (e. g., UV) it is necessary to use an interrupt vector 
> as a "system" vector, that is, it is generated by system hardware, not 
> an IO device.  This patch dynamically allocates them from the pool of 
> interrupt vectors below the fixed system vectors.  This may include 
> stealing some from the device interrupt vector pool, so they are 
> allocated dynamically so that other archs don't have to pay the price.  
> In UV, examples of these hardware and software systems that need 
> dynamically allocated vectors are the GRU, the BAU, and XPM/XPC.

patch has severe inlined-as-text corruption, please check 
Documentation/email-clients.txt about how to send patches. (or send it 
as an attachment, i can process that)

Also, given the extensive feedback from Eric, it would be nice to have 
his Acked-by line as well to any patch that is resubmitted for 
inclusion, to make sure you meet all the requirements he has outlined.

Thanks,

	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/