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

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: <m13alp1z8w.fsf@frodo.ebiederm.org>
Date:	Thu, 31 Jul 2008 15:10:23 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Alan Mayer <ajm@....com>
Cc:	jeremy@...p.org, rusty@...tcorp.com.au, suresh.b.siddha@...el.com,
	mingo@...e.hu, torvalds@...ux-foundation.org,
	linux-kernel@...r.kernel.org, Dean Nelson <dcn@....com>,
	Cliff Wickman <cpw@....com>
Subject: Re: [PATCH] x86_64:  Dynamically allocate arch specific system vectors

Alan Mayer <ajm@....com> writes:

> Subject: [PATCH] x86_64:  Dynamically allocate arch specific system vectors
>
> From: Alan Mayer <ajm@....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
--
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/