linux-kernel - Re: [PATCH] Cell SPU task notification -- updated patch: #1

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: <45AC02A4.8080301@us.ibm.com>
Date:	Mon, 15 Jan 2007 16:39:32 -0600
From:	Maynard Johnson <maynardj@...ibm.com>
To:	michael@...erman.id.au
CC:	cbe-oss-dev@...abs.org, linux-kernel@...r.kernel.org,
	linuxppc-dev@...abs.org, Arnd Bergmann <arnd.bergmann@...ibm.com>
Subject: Re: [PATCH] Cell SPU task notification -- updated patch: #1

Attached is an updated patch that addresses Michael Ellerman's comments.

One comment made by Michael has not yet been addressed:
The comment was in regard to the for-loop in 
spufs/sched.c:notify_spus_active().  He wondered if the scheduler can 
swap a context from one node to another.  If so, there's a small window 
in this loop (where we switch the lock from one node's active list to 
the next) where it may be possible we might miss waking up a context and 
send a spurious wakeup to another.
	Arnd . . . can you comment on this question?

Thanks.
-Maynard


View attachment "spu-notifier.patch" of type "text/x-diff" (4286 bytes)