linux-kernel - Re: [PATCH] x86_64: Change FIRST_SYSTEM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <86802c440804091328s4127422dk593384c32ba56e88@mail.gmail.com>
Date:	Wed, 9 Apr 2008 13:28:09 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Ingo Molnar" <mingo@...e.hu>,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Cc:	"Alan Mayer" <ajm@....com>, torvalds@...ux-foundation.org,
	"linux-kernel list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86_64: Change FIRST_SYSTEM_VECTOR to a variable.

On Wed, Apr 9, 2008 at 7:59 AM, Ingo Molnar <mingo@...e.hu> wrote:
>
>  * Alan Mayer <ajm@....com> wrote:
>
>  > Subject: [PATCH] x86_64: Change FIRST_SYSTEM_VECTOR to a variable.
>  >
>  > From: Alan Mayer <ajm@....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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/