linux-kernel - Re: [PATCH] affinity is not defined in non-smp kernels

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: <m1y7mif8j4.fsf@ebiederm.dsl.xmission.com>
Date:	Wed, 28 Feb 2007 11:21:03 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Bill Davidsen <davidsen@....com>
Cc:	Fernando Luis Vázquez Cao 
	<fernando@....ntt.co.jp>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	ak@...e.de, akpm@...ux-foundation.org
Subject: Re: [PATCH] affinity is not defined in non-smp kernels - i386

Bill Davidsen <davidsen@....com> writes:

> Eric W. Biederman wrote:
>> Fernando Luis Vázquez Cao <fernando@....ntt.co.jp> writes:
>>
>>> Initialize affinity only when building SMP kernels.
>>
>> Reasonable.  I goofed here.
>>
>> However I would prefer my patch that just deletes these problem lines.
>> These lines don't really contribute anything and are harmless to
>> remove.
>
> Where is the initialization performed, then?

The field is initialized statically.   We also never use it internally it the
kernel except for reporting back to the user what where we were told we could
route the interrupt to.

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/