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
| ||
|
Date: Mon, 19 May 2014 11:49:08 -0700 From: John Stultz <john.stultz@...aro.org> To: Maarten Lankhorst <maarten.lankhorst@...onical.com> Cc: lkml <linux-kernel@...r.kernel.org>, linux-arch@...r.kernel.org, "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>, "linaro-mm-sig@...ts.linaro.org" <linaro-mm-sig@...ts.linaro.org>, Colin Cross <ccross@...gle.com>, linux-media@...r.kernel.org, Rom Lemarchand <romlem@...gle.com>, Greg Hackmann <ghackmann@...gle.com> Subject: Re: [PATCH 4/6] android: convert sync to fence api, v5 On Mon, Feb 24, 2014 at 8:29 AM, Maarten Lankhorst <maarten.lankhorst@...onical.com> wrote: > Just to show it's easy. > > Android syncpoints can be mapped to a timeline. This removes the need > to maintain a separate api for synchronization. I've left the android > trace events in place, but the core fence events should already be > sufficient for debugging. > > v2: > - Call fence_remove_callback in sync_fence_free if not all fences have fired. > v3: > - Merge Colin Cross' bugfixes, and the android fence merge optimization. > v4: > - Merge with the upstream fixes. > v5: > - Fix small style issues pointed out by Thomas Hellstrom. > > Signed-off-by: Maarten Lankhorst <maarten.lankhorst@...onical.com> I ran this through a fairly simple unit test for the Android sw_sync interface and it ran fine. Also since Colin, Rom and Greg didn't seem to have major objections last I spoke with them: Acked-by: John Stultz <john.stultz@...aro.org> thanks -john -- 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/
Powered by blists - more mailing lists