Re: [Intel-gfx] [PATCH 1/5] drm/i915/guc: Don't GEM_BUG_ON on corrupted G2H CTB

2020-01-16 Thread Daniele Ceraolo Spurio
On 1/16/20 11:13 AM, Michal Wajdeczko wrote: On Thu, 16 Jan 2020 19:46:35 +0100, Daniele Ceraolo Spurio wrote: On 1/15/20 6:08 AM, Michal Wajdeczko wrote: We should never BUG_ON on any corruption in CTB descriptor as data there can be also modified by the GuC. Instead we can use flag

Re: [Intel-gfx] [PATCH 1/5] drm/i915/guc: Don't GEM_BUG_ON on corrupted G2H CTB

2020-01-16 Thread Michal Wajdeczko
On Thu, 16 Jan 2020 19:46:35 +0100, Daniele Ceraolo Spurio wrote: On 1/15/20 6:08 AM, Michal Wajdeczko wrote: We should never BUG_ON on any corruption in CTB descriptor as data there can be also modified by the GuC. Instead we can use flag "is_in_error" to indicate that we will not

Re: [Intel-gfx] [PATCH 1/5] drm/i915/guc: Don't GEM_BUG_ON on corrupted G2H CTB

2020-01-16 Thread Daniele Ceraolo Spurio
On 1/15/20 6:08 AM, Michal Wajdeczko wrote: We should never BUG_ON on any corruption in CTB descriptor as data there can be also modified by the GuC. Instead we can use flag "is_in_error" to indicate that we will not process any further messages over this CTB (until reset). While here move

[Intel-gfx] [PATCH 1/5] drm/i915/guc: Don't GEM_BUG_ON on corrupted G2H CTB

2020-01-15 Thread Michal Wajdeczko
We should never BUG_ON on any corruption in CTB descriptor as data there can be also modified by the GuC. Instead we can use flag "is_in_error" to indicate that we will not process any further messages over this CTB (until reset). While here move descriptor error reporting to the function that