On 12/04/2023 14:10, Rodrigo Vivi wrote:
On Wed, Apr 12, 2023 at 12:56:26PM +0200, Andi Shyti wrote:
Hi Rodrigo,
Currently, when we perform operations such as clearing or copying
large blocks of memory, we generate multiple requests that are
executed in a chain.
However, if one of these requests fails, we may not realize it
unless it happens to be the last request in the chain. This is
because errors are not properly propagated.
For this we need to keep propagating the chain of fence
notification in order to always reach the final fence associated
to the final request.
To address this issue, we need to ensure that the chain of fence
notifications is always propagated so that we can reach the final
fence associated with the last request. By doing so, we will be
able to detect any memory operation failures and determine
whether the memory is still invalid.
On copy and clear migration signal fences upon completion.
On copy and clear migration, signal fences upon request
completion to ensure that we have a reliable perpetuation of the
operation outcome.
Fixes: cf586021642d80 ("drm/i915/gt: Pipelined page migration")
Reported-by: Matthew Auld <matthew.auld@xxxxxxxxx>
Suggested-by: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
Signed-off-by: Andi Shyti <andi.shyti@xxxxxxxxxxxxxxx>
Cc: stable@xxxxxxxxxxxxxxx
Try to find from which kernel version this needs to go in. For instance
if we look at cf586021642d80 it would be v5.15+, but actually in that
commit there are no users apart from selftests. So I think find the
first user which can be user facing and mark the appropriate kernel
version in the stable tag.
Reviewed-by: Matthew Auld <matthew.auld@xxxxxxxxx>
With Matt's comment regarding missing lock in intel_context_migrate_clear
addressed, this is:
Acked-by: Nirmoy Das <nirmoy.das@xxxxxxxxx>
Nack!
Please get some ack from Joonas or Tvrtko before merging this series.
There is no architectural change... of course, Joonas and Tvrtko
are more than welcome (and actually invited) to look into this
patch.
And, btw, there are still some discussions ongoing on this whole
series, so that I'm not going to merge it any time soon. I'm just
happy to revive the discussion.
It is a big series targeting stable o.O where the revisions in the cover
letter are not helping me to be confident that this is the right approach
instead of simply reverting the original offending commit:
cf586021642d ("drm/i915/gt: Pipelined page migration")
Why should we remove all the migration completely? What about the
copy?
Is there any other alternative that doesn't hurt the Linux stable rules?
I honestly fail to see this one here is "obviously corrected and tested"
and it looks to me that it has more "than 100 lines, with context".
Does this series really "fix only one thing" with 5 patches?
This is challenging.
Fix to me looks needed on the high level (haven't read the patch details
yet), but when a series sent to stable can go quite badly and we had
such problem very recently with only a two patch series. And it is also
indeed quite large.
Reverting cf586021642d80 definitely isn't an option because stuff
depends on the code added by it and would need an alternative
implementation. Losing async clear/migrate which would be bad and could
also a large patch to implement the alternative.
So since I think we are indeed stuck with fixing this - would it be
better to squash it all into one patch for easier backporting?
We can also look if there are ways to make the diff smaller.
Regards,
Tvrtko
It looks to me that we are adding magic on top of magic to workaround
the deadlocks, but then adding more waits inside locks... And this with
the hang checks vs heartbeats, is this really an issue on current upstream
code? or was only on DII?
There is no real magic happening here. It's just that the error
message was not reaching the end of the operation while this
patch is passing it over.
Where was the bug report to start with?
Matt has reported this, I will give to you the necessary links to
it offline.
It would be really good to have a report to see if this is
"real bug that bothers people (not a, “This could be a problem…” type thing)."
All quotes above are from:
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
Thanks for looking into this,
Andi
