Quoting Mika Kuoppala (2020-02-05 14:50:58)
> Chris Wilson writes:
>
> > Currently on execlists, we use a local hwsp for the kernel_context,
> > rather than the engine's HWSP, as this is the default for execlists.
> > However, seqno rollover requires allocating a new HWSP cachline, and may
>
> s
Chris Wilson writes:
> Currently on execlists, we use a local hwsp for the kernel_context,
> rather than the engine's HWSP, as this is the default for execlists.
> However, seqno rollover requires allocating a new HWSP cachline, and may
s/cachline/cacheline
-Mika
___
Currently on execlists, we use a local hwsp for the kernel_context,
rather than the engine's HWSP, as this is the default for execlists.
However, seqno rollover requires allocating a new HWSP cachline, and may
require pinning a new HWSP page in the GTT. This operation requiring
pinning in the GGTT
Currently on execlists, we use a local hwsp for the kernel_context,
rather than the engine's HWSP, as this is the default for execlists.
However, seqno rollover requires allocating a new HWSP cachline, and may
require pinning a new HWSP page in the GTT. This operation requiring
pinning in the GGTT
