Date: Mon, 11 Aug 2008 18:59:30 +0200
From: Ingo Molnar <mingo@elte.hu>
To: Alan Mayer <ajm@sgi.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>, jeremy@goop.org,
       rusty@rustcorp.com.au, suresh.b.siddha@intel.com,
       torvalds@linux-foundation.org, linux-kernel@vger.kernel.org,
       Dean Nelson <dcn@sgi.com>, Cliff Wickman <cpw@sgi.com>,
       "H. Peter Anvin" <hpa@zytor.com>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] x86_64:  (NEW) Dynamically allocate arch specific
	system vectors
Message-ID: <20080811165930.GI4524@elte.hu>
References: <489C6844.9050902@sgi.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <489C6844.9050902@sgi.com>
User-Agent: Mutt/1.5.18 (2008-05-17)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1368
Lines: 33


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

> Subject: [PATCH] x86_64: (NEW) Dynamically allocate arch specific 
> system vectors
>
> From: Alan Mayer <ajm@sgi.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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/