linux-kernel - Re: [RFC 0/4] 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: <m17i9a61l2.fsf@frodo.ebiederm.org>
Date:	Wed, 17 Sep 2008 11:59:05 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Dimitri Sivanich <sivanich@....com>
Cc:	Ingo Molnar <mingo@...e.hu>, Dean Nelson <dcn@....com>,
	Alan Mayer <ajm@....com>, jeremy@...p.org,
	rusty@...tcorp.com.au, suresh.b.siddha@...el.com,
	torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org,
	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Yinghai Lu <Yinghai.lu@....com>
Subject: Re: [RFC 0/4] dynamically allocate arch specific system vectors

Dimitri Sivanich <sivanich@....com> writes:

> On Tue, Sep 16, 2008 at 03:46:54PM -0500, Dean Nelson wrote:
>> On Tue, Sep 16, 2008 at 10:24:48AM +0200, Ingo Molnar wrote:
>> > 
>> > * Dean Nelson <dcn@....com> wrote:
>> > 
>> > > > while i understand the UV_BAU_MESSAGE case (TLB flushes are 
>> > > > special), why does sgi-gru and sgi-xp need to go that deep? They are 
>> > > > drivers, they should be able to make use of an ordinary irq just 
>> > > > like the other 2000 drivers we have do.
>> > > 
>> > > The sgi-gru driver needs to be able to allocate a single irq/vector 
>> > > pair for all CPUs even those that are not currently online. The sgi-xp 
>> > > driver has similar but not as stringent needs.

I need to look at these patches some more (apologies I got busy).

We can not assign a vector to all CPUS.

We don't have the fields for vector -> irq mapping for cpus that
are not-online.  So we can only assign to cpus that are online now.
And latter add the other cpus when they come online.

I have had that oops, it sucks, I don't want to go back.

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/