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>
Subject: Re: [PATCH] x86_64: Dynamically allocate arch specific system vectors
Date: Thu, 31 Jul 2008 15:10:23 -0700 [thread overview]
Message-ID: <m13alp1z8w.fsf@frodo.ebiederm.org> (raw)
In-Reply-To: <48922D16.1080704@sgi.com> (Alan Mayer's message of "Thu, 31 Jul 2008 16:22:30 -0500")
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
next prev parent reply other threads:[~2008-07-31 22:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 21:22 Alan Mayer
2008-07-31 22:10 ` Eric W. Biederman [this message]
2008-08-01 15:51 ` Cliff Wickman
2008-08-01 21:00 ` Eric W. Biederman
2008-08-01 21:51 ` Alan Mayer
2008-08-01 22:14 ` Eric W. Biederman
2008-08-04 19:37 ` Alan Mayer
2008-08-04 20:39 ` Mike Travis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m13alp1z8w.fsf@frodo.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=ajm@sgi.com \
--cc=cpw@sgi.com \
--cc=dcn@sgi.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=suresh.b.siddha@intel.com \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome