[PATCH v2] sync_file: Return consistent status in SYNC_IOC_FILE_INFO

2017-10-09 Thread John Einar Reitan
showing non-signaled underlying fences but an overall signaled state. This patch changes sync_file_ioctl_fence_info to track what has been encoded and using that as the overall sync_file status. Tested-by: Vamsidhar Reddy Gaddam <vamsidhar.gad...@arm.com> Signed-off-by: John Einar

Re: [PATCH] sync_file: Return consistent status in SYNC_IOC_FILE_INFO

2017-10-04 Thread John Einar Reitan
On Wed, Oct 04, 2017 at 11:43:23AM +0100, Chris Wilson wrote: > In hindsight, having both the per-fence and global variable be called > info was a mistake. Certainly made this diff a little harder to parse > than required! I agree, I had to re-read the code a few times to find & fix the bug. >

[PATCH] sync_file: Return consistent status in SYNC_IOC_FILE_INFO

2017-10-04 Thread John Einar Reitan
showing non-signaled underlying fences but an overall signaled state. This patch changes sync_file_ioctl_fence_info to track what has been encoded and using that as the overall sync_file status. Tested-by: Vamsidhar Reddy Gaddam <vamsidhar.gad...@arm.com> Signed-off-by: John Einar

[PATCH] sync_file: Return consistent status in SYNC_IOC_FILE_INFO

2017-10-04 Thread John Einar Reitan
showing non-signaled underlying fences but an overall signaled state. This patch changes sync_file_ioctl_fence_info to track what has been encoded and using that as the overall sync_file status. Tested-by: Vamsidhar Reddy Gaddam <vamsidhar.gad...@arm.com> Signed-off-by: John Einar

[PATCH v10 0/3] Secure Memory Allocation Framework

2016-10-10 Thread John Einar Reitan
On Fri, Oct 07, 2016 at 10:42:17AM -0400, Rob Clark wrote: > probably should keep the discussion on github (USAGE.md was updated a > bit more and merged into https://github.com/cubanismo/allocator so > look there for the latest).. > > but briefly: > > 1) my expectation is if the user is