Re: [PATCH i-g-t] tests/kms_busy: Only test agains one engine

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Op 03-08-17 om 14:05 schreef Daniel Vetter:
> Back when we used cs flips it made sense to go through different
> engines, since a buffer busy on an engine that we couldnt' use for
> cs flipping ended up in different paths.
>
> But with atomic we use a worker for all flips, and going through the
> combinatorial growth of engines just wastes precious machine time.
> More so the more modern the platform is.
>
> Of course gem tests should still do some diagonal testing across all
> engines, but the kms side can afford to be a bit cheaper.
>
> Cc: Chris Wilson <chris@xxxxxxxxxxxxxxxxxx>
> Cc: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@xxxxxxxxx>
> Signed-off-by: Daniel Vetter <daniel.vetter@xxxxxxxxx>
> ---
Acked-by: Maarten Lankhorst <maarten.lankhorst@xxxxxxxxxxxxxxx>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux