Re: [PATCH] x86_64: Dynamically allocate arch specific system vectors

[Eric W. Biederman]

Alan Mayer <ajm@xxxxxxx> writes:

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