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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080409145945.GB17100@elte.hu>
Date:	Wed, 9 Apr 2008 16:59:45 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Alan Mayer <ajm@....com>
Cc:	torvalds@...ux-foundation.org,
	linux-kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86_64: Change FIRST_SYSTEM_VECTOR to a variable.


* 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?

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