Claude review: drm/v3d: Attach per-fd reset counters to v3d_stats

[Claude Code Review Bot <claude-review@example.com>]

Patch Review

Moving the per-fd reset counter into `v3d_stats` is the natural follow-up. Since `v3d_stats` now outlives the fd (via job references), the reset can safely increment the counter through `job->client_stats->reset_counter` without needing the `file_priv` NULL check.

Using `atomic_t` for both global and per-fd reset counters is appropriate - they're incremented under `reset_lock` but read without it, so atomics provide the necessary visibility.

The `CONTEXT_RESET_COUNTER` ioctl now sums across all queues:

```c
	args->value = 0;
	for (enum v3d_queue q = 0; q < V3D_MAX_QUEUES; q++)
		args->value += atomic_read(&v3d_priv->stats[q]->reset_counter);
```

This is a slight semantic change from the old per-fd single counter: a single GPU reset previously incremented `v3d_priv->reset_counter` once, but now it increments only the specific queue's stats `reset_counter`. Since `v3d_gpu_reset_for_timeout` increments `job->client_stats->reset_counter` (one specific queue), and the ioctl sums all queues, the total should still reflect one increment per reset caused by this fd. This looks correct.

The big cleanup in `v3d_postclose` removing the `file_priv` NULL-ing dance is the main simplification goal of the series, and it's well-justified at this point.

No issues.

---
Generated by Claude Code Patch Reviewer