Re: [Intel-gfx] [PATCH 06/12] drm/i915: Populate ctx ID for periodic OA reports

2017-07-31 Thread kbuild test robot
Hi Sourab, [auto build test WARNING on drm-intel/for-linux-next] [also build test WARNING on next-20170731] [cannot apply to v4.13-rc3] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Sagar-Arun-

Re: [Intel-gfx] [PATCH 06/12] drm/i915: Populate ctx ID for periodic OA reports

2017-07-31 Thread Kamble, Sagar A
Read B2.end report -Original Message- From: Landwerlin, Lionel G Sent: Monday, July 31, 2017 2:57 PM To: Kamble, Sagar A ; intel-gfx@lists.freedesktop.org Cc: Sourab Gupta Subject: Re: [Intel-gfx] [PATCH 06/12] drm/i915: Populate ctx ID for periodic OA reports Hi Sagar, I'm curi

Re: [Intel-gfx] [PATCH 06/12] drm/i915: Populate ctx ID for periodic OA reports

2017-07-31 Thread Lionel Landwerlin
Hi Sagar, I'm curious to what happens if 2 contexts submit requests which a time period smaller than the sampling OA period on Gen7.5. My understanding is that with this change you'll only retain the last submission and then the ctx_id reported in the SAMPLE_CTX_ID field will be incorrect for

[Intel-gfx] [PATCH 06/12] drm/i915: Populate ctx ID for periodic OA reports

2017-07-31 Thread Sagar Arun Kamble
From: Sourab Gupta This adds support for populating the ctx id for the periodic OA reports when requested through the corresponding property. For Gen8, the OA reports itself have the ctx ID and it is the one programmed into HW while submitting workloads. Thus it's retrieved from reports itself.