From: ebiederm@xmission.com (Eric W. Biederman)
To: Alan Mayer <ajm@sgi.com>
Cc: jeremy@goop.org, rusty@rustcorp.com.au, suresh.b.siddha@intel.com,
       mingo@elte.hu, torvalds@linux-foundation.org,
       linux-kernel@vger.kernel.org, Dean Nelson <dcn@sgi.com>,
       Cliff Wickman <cpw@sgi.com>
References: <48922D16.1080704@sgi.com>
Date: Thu, 31 Jul 2008 15:10:23 -0700
In-Reply-To: <48922D16.1080704@sgi.com> (Alan Mayer's message of "Thu, 31 Jul
	2008 16:22:30 -0500")
Message-ID: <m13alp1z8w.fsf@frodo.ebiederm.org>
User-Agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: [PATCH] x86_64:  Dynamically allocate arch specific system vectors
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1121
Lines: 26

Alan Mayer <ajm@sgi.com> writes:

> Subject: [PATCH] x86_64:  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.

Could you please explain words why the vector allocator does not work
for you?

This code at first glance looks a lot like duplicating the vector allocator.

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