Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760226AbaGPS6B (ORCPT ); Wed, 16 Jul 2014 14:58:01 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:53684 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753854AbaGPS56 (ORCPT ); Wed, 16 Jul 2014 14:57:58 -0400 Date: Wed, 16 Jul 2014 12:02:32 -0700 From: Greg KH To: Daniel Vetter Cc: "Bridgman, John" , Jerome Glisse , "Lewycky, Andrew" , "linux-kernel@vger.kernel.org" , "dri-devel@lists.freedesktop.org" , "Deucher, Alexander" , "akpm@linux-foundation.org" , Maarten Lankhorst , "linaro-mm-sig@lists.linaro.org" Subject: Re: [PATCH 00/83] AMD HSA kernel driver Message-ID: <20140716190232.GB31046@kroah.com> References: <019CCE693E457142B37B791721487FD9180A193B@storexdag01.amd.com> <20140713035535.GB5301@gmail.com> <20140713164901.GB10624@gmail.com> <53C396D3.9000600@vodafone.de> <20140715173704.GA3421@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jul 16, 2014 at 10:21:14AM +0200, Daniel Vetter wrote: > On Tue, Jul 15, 2014 at 7:53 PM, Bridgman, John wrote: > [snip away the discussion about hsa device discover, I'm hijacking > this thread just for the event/fence stuff here.] > > > ... There's an event mechanism still to come - mostly for communicating fences and shader interrupts back to userspace, but also used for "device change" notifications, so no polling of sysfs. > > That could would be interesting. On i915 my plan is to internally use > the recently added struct fence from Maarten. For the external > interface for userspace that wants explicit control over fences I'm > leaning towards polishing the android syncpt stuff (currently in > staging). But in any case I _really_ want to avoid that we end up with > multiple different and incompatible explicit fencing interfaces on > linux. I agree, and I'll say it stronger than that, we WILL NOT have different and incompatible fencing interfaces in the kernel. That way lies madness. John, take a look at what is now in linux-next, it should provide what you need here, right? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/