[PATCH 1/3] nvkm/gsp: correctly advance the read pointer of GSP message queue

A GSP event message consists three parts: message header, RPC header, message body. GSP calculates the number of pages to write from the total size of a GSP message. This behavior can be observed from the movement of the write pointer. However, nvkm takes only the size of RPC header and message bo

Re: [PATCH 1/3] nvkm/gsp: correctly advance the read pointer of GSP message queue

Hi Zhi, On Sun, Sep 22, 2024 at 06:07:07AM -0700, Zhi Wang wrote: > A GSP event message consists three parts: message header, RPC header, > message body. GSP calculates the number of pages to write from the > total size of a GSP message. This behavior can be observed from the > movement of the wri

[PATCH 1/3] nvkm/gsp: correctly advance the read pointer of GSP message queue

A GSP event message consists three parts: message header, RPC header, message body. GSP calculates the number of pages to write from the total size of a GSP message. This behavior can be observed from the movement of the write pointer. However, nvkm takes only the size of RPC header and message bo