Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-09 Thread Yang, Rong R
sktop.org > Subject: Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event > status. > > > The spec only says if event is not in CL_COMPLETE status, it will get > CL_PROFILING_INFO_NOT_AVAILABLE. It doesn't mean a clFinish() should > update all events status. Ac

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Zhigang Gong
ntProfilingInfo could query all event > status. > > > > > -Original Message- > > From: Zhigang Gong [mailto:zhigang.g...@linux.intel.com] > > Sent: Wednesday, August 5, 2015 12:49 > > To: Yang, Rong R; Luo, Xionghu > > Cc: beignet@lists.freedesktop.

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Yang, Rong R
> -Original Message- > From: Zhigang Gong [mailto:zhigang.g...@linux.intel.com] > Sent: Wednesday, August 5, 2015 12:49 > To: Yang, Rong R; Luo, Xionghu > Cc: beignet@lists.freedesktop.org > Subject: RE: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Zhigang Gong
sktop.org > Subject: Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event > status. > > The root cause of beignet using on-demand manner is no point to update > event's status. If there have this point, I think there is no side effect to > update > the status

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Yang, Rong R
sue. > > Thanks, > Zhigang Gong. > > > -Original Message- > > From: Beignet [mailto:beignet-boun...@lists.freedesktop.org] On Behalf > > Of Yang, Rong R > > Sent: Tuesday, August 4, 2015 3:31 PM > > To: Zhigang Gong; Luo, Xionghu > > Cc

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Zhigang Gong
n...@lists.freedesktop.org] On Behalf Of > Yang, Rong R > Sent: Tuesday, August 4, 2015 3:31 PM > To: Zhigang Gong; Luo, Xionghu > Cc: beignet@lists.freedesktop.org > Subject: Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event > status. > > I

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-04 Thread Yang, Rong R
FILING_INFO_NOT_AVAILABLE. > -Original Message- > From: Beignet [mailto:beignet-boun...@lists.freedesktop.org] On Behalf Of > Zhigang Gong > Sent: Tuesday, August 4, 2015 13:28 > To: Luo, Xionghu > Cc: beignet@lists.freedesktop.org > Subject: Re: [Beignet] [PATCH v

Re: [Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-03 Thread Zhigang Gong
The spec only says if event is not in CL_COMPLETE status, it will get CL_PROFILING_INFO_NOT_AVAILABLE. It doesn't mean a clFinish() should update all events status. According to the spec, clFinish() only need to make sure the previously enqueued task has been processed and completed. Form my poin

[Beignet] [PATCH v2] GetEventProfilingInfo could query all event status.

2015-08-03 Thread xionghu . luo
From: Luo Xionghu this could fix the shoc project reported CL_PROFILING_INFO_NOT_AVAILABLE issue. https://github.com/vetter/shoc/issues/47 v2: per spec, the GetEventProfilingInfo need return CL_PROFILING_INFO_NOT_AVAILABLE if the event is not CL_COMPLETE, so the event should be updated in clFinis