UPSTREAM: drm/virtio: implement context init: stop using drv->context when creating fence

The plumbing is all here to do this.  Since we always use the
default fence context when allocating a fence, this makes no
functional difference.

We can't process just the largest fence id anymore, since it's
it's associated with different timelines.  It's fine for fence_id
260 to signal before 259.  As such, process each fence_id
individually.

Signed-off-by: Gurchetan Singh <gurchetansingh@chromium.org>
Acked-by: Lingfeng Yang <lfy@google.com>
Link: http://patchwork.freedesktop.org/patch/msgid/20210921232024.817-9-gurchetansingh@chromium.org


Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
(cherry picked from commit bbf588d7)

BUG=b:176158390, b:203009046, b:230100768
TEST=gfxbench and deqp-cts in arcvm

Signed-off-by: Rob Clark <robdclark@chromium.org>
Change-Id: Id9739f7695debd5c71c7adebc438c3944c1a3880
Disallow-Recycled-Builds: test-failures
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/third_party/kernel/+/3469487


Reviewed-by: Sean Paul <seanpaul@chromium.org>
Reviewed-by: Chia-I Wu <olv@google.com>
Reviewed-by: Ryan Neph <ryanneph@google.com>