From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>,
"Eric W. Biederman" <ebiederm@xmission.com>
Cc: "Alan Mayer" <ajm@sgi.com>,
torvalds@linux-foundation.org,
"linux-kernel list" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86_64: Change FIRST_SYSTEM_VECTOR to a variable.
Date: Wed, 9 Apr 2008 13:28:09 -0700 [thread overview]
Message-ID: <86802c440804091328s4127422dk593384c32ba56e88@mail.gmail.com> (raw)
In-Reply-To: <20080409145945.GB17100@elte.hu>
On Wed, Apr 9, 2008 at 7:59 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Alan Mayer <ajm@sgi.com> wrote:
>
> > Subject: [PATCH] x86_64: Change FIRST_SYSTEM_VECTOR to a variable.
> >
> > From: Alan Mayer <ajm@sgi.com>
> >
> > The SGI UV system needs several more system vectors than a vanilla
> > x86_64 system. Rather than burden the other archs with extra system
> > vectors that they don't use, change FIRST_SYSTEM_VECTOR to a variable,
> > so that it can be dynamic.
>
> nice - but please split this up into two patches: first one that changes
> the generic code to use a variable limit - this patch will (should) be a
> functional NOP.
>
> then a second patch adds those two new UV vectors.
>
> Also, could you please also change the 32-bit side as well so that we at
> least keep the two implementations roughly in sync?
>
for x86_64, current from 0x20 to 0x2f, we only use one for irq migration.
wonder if you can use 2 from them for UV...
YH
next prev parent reply other threads:[~2008-04-09 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-08 21:10 Alan Mayer
2008-04-09 14:59 ` Ingo Molnar
2008-04-09 15:06 ` Alan Mayer
2008-04-09 20:28 ` Yinghai Lu [this message]
2008-04-09 20:31 ` Alan Mayer
2008-04-09 21:33 Alan Mayer
2008-04-09 22:08 ` Linus Torvalds
2008-04-10 15:22 ` Alan Mayer
2008-04-15 20:36 Alan Mayer
2008-04-16 13:19 ` Ingo Molnar
2008-04-16 20:17 ` Alan Mayer
2008-04-21 15:46 ` Ingo Molnar
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=86802c440804091328s4127422dk593384c32ba56e88@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ajm@sgi.com \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®