linux-kernel - Re: [PATCH] fix dynticks for voyager

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: <4637DA9F.3030503@goop.org>
Date:	Tue, 01 May 2007 17:26:07 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Matt Mackall <mpm@...enic.com>
CC:	James Bottomley <James.Bottomley@...senPartnership.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] fix dynticks for voyager

Matt Mackall wrote:
> On Mon, Apr 30, 2007 at 11:38:51AM -0500, James Bottomley wrote:
>   
>> As usual voyager tripped over an explicit boot CPU is zero assumption in
>> the dynticks code.  This is the fix I have queued in the voyager tree.
>>     
>
> Can we flush out all these assumptions by adding a constant offset
> somewhere? Or reversing the ordering?
>   

My understanding is that the boot CPU is random depending on who wins
the "I get to boot" bunfight.

    J

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