On 7/20/2016 2:42 PM, Chris Wilson wrote:
On Wed, Jul 20, 2016 at 09:51:45AM +0530, Goel, Akash wrote:
On 7/19/2016 4:51 PM, Chris Wilson wrote:
On Tue, Jul 19, 2016 at 12:12:20PM +0100, Tvrtko Ursulin wrote:
On 10/07/16 14:41, akash.g...@intel.com wrote:
From: Sagar Arun Kamble
If GuC
On Wed, Jul 20, 2016 at 09:51:45AM +0530, Goel, Akash wrote:
>
>
> On 7/19/2016 4:51 PM, Chris Wilson wrote:
> >On Tue, Jul 19, 2016 at 12:12:20PM +0100, Tvrtko Ursulin wrote:
> >>
> >>On 10/07/16 14:41, akash.g...@intel.com wrote:
> >>>From: Sagar Arun Kamble
> >>>
> >>>If GuC logs are being ca
On 7/19/2016 4:51 PM, Chris Wilson wrote:
On Tue, Jul 19, 2016 at 12:12:20PM +0100, Tvrtko Ursulin wrote:
On 10/07/16 14:41, akash.g...@intel.com wrote:
From: Sagar Arun Kamble
If GuC logs are being captured, there should be a force log buffer flush
action sent to GuC before proceeding wit
On Tue, Jul 19, 2016 at 12:12:20PM +0100, Tvrtko Ursulin wrote:
>
> On 10/07/16 14:41, akash.g...@intel.com wrote:
> >From: Sagar Arun Kamble
> >
> >If GuC logs are being captured, there should be a force log buffer flush
> >action sent to GuC before proceeding with GPU reset and re-initializing
On 10/07/16 14:41, akash.g...@intel.com wrote:
From: Sagar Arun Kamble
If GuC logs are being captured, there should be a force log buffer flush
action sent to GuC before proceeding with GPU reset and re-initializing
GUC. Those logs would be useful to understand why the GPU reset was
initiated.
From: Sagar Arun Kamble
If GuC logs are being captured, there should be a force log buffer flush
action sent to GuC before proceeding with GPU reset and re-initializing
GUC. Those logs would be useful to understand why the GPU reset was
initiated.
v2: Rebase.
Signed-off-by: Sagar Arun Kamble
S
