gpu: nova-core: Fixups for GSP message queue and bindings
Subsystems (4)
Alexandre Courbot
maintainercover gpu: nova-core: Fixups for GSP message queue and bindings
This series contains a few fixups for the recently merged GSP command-queue code, by order of importance:
- Some explicit padding required to safely implement AsBytes was missing in the bindings,
- A bug in the received message length calculation results in the message handler being given more data than it should,
- MaybeZeroable is now derived by the kernel's bindgen, but the Nova bindings have not been updated for that,
- Some items in the bindings were referred to using the version module directly, instead of the alias we defined to limit the diff when we upgrade firmware versions.
All of them address "bugs" (with the first two fixing actual correctness issues), but since Nova does not do much anyway, they are also not absolutely critical and can wait -rc1 if we prefer to do so.
---
Alexandre Courbot (4):
gpu: nova-core: bindings: Add missing explicit padding
gpu: nova-core: gsp: Fix length of received messages
gpu: nova-core: bindings: Derive MaybeZeroable
gpu: nova-core: gsp: Replace firmware version with "bindings" alias
drivers/gpu/nova-core/gsp/cmdq.rs | 11 ++- drivers/gpu/nova-core/gsp/fw.rs | 67 +++++++------- drivers/gpu/nova-core/gsp/fw/r570_144.rs | 11 ++- drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs | 105 ++++++++++++---------- 4 files changed, 103 insertions(+), 91 deletions(-)
---
base-commit: 57dc2ea0b7bdb828c5d966d9135c28fe854933a4
change-id: 20251121-nova-fixes-dc9b4f17b90e
Best regards,
Signature · 1 line
Alexandre Courbot <[email protected]>
Alexandre Courbot
maintainerPATCH 1/4 gpu: nova-core: bindings: Add missing explicit padding
Explicit padding is needed in order to avoid uninitialized bytes and safely implement AsBytes. The --explicit-padding of bindgen was omitted by mistake when these bindings were generated.
--- drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs | 12 ++++++++++++ 1 file changed, 12 insertions(+)
drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs +12 -0
@@ -325,6 +325,7 @@ pub struct NV0080_CTRL_GPU_GET_SRIOV_CAPS_PARAMS { pub totalVFs: u32_, pub firstVfOffset: u32_, pub vfFeatureMask: u32_, + pub __bindgen_padding_0: [u8; 4usize], pub FirstVFBar0Address: u64_, pub FirstVFBar1Address: u64_, pub FirstVFBar2Address: u64_,
@@ -340,6 +341,7 @@ pub struct NV0080_CTRL_GPU_GET_SRIOV_CAPS_PARAMS { pub bClientRmAllocatedCtxBuffer: u8_, pub bNonPowerOf2ChannelCountSupported: u8_, pub bVfResizableBAR1Supported: u8_, + pub __bindgen_padding_1: [u8; 7usize], }#[repr( C )] #[derive( Debug , Default , Copy , Clone )]
@@ -347,11 +349,13 @@ pub struct NV2080_CTRL_BIOS_GET_SKU_INFO_PARAMS { pub BoardID: u32_, pub chipSKU: [ffi::c_char; 9usize], pub chipSKUMod: [ffi::c_char; 5usize], + pub __bindgen_padding_0: [u8; 2usize], pub skuConfigVersion: u32_, pub project: [ffi::c_char; 5usize], pub projectSKU: [ffi::c_char; 5usize], pub CDP: [ffi::c_char; 6usize], pub projectSKUMod: [ffi::c_char; 2usize], + pub __bindgen_padding_1: [u8; 2usize], pub businessCycle: u32_, }pub type NV2080_CTRL_CMD_FB_GET_FB_REGION_SURFACE_MEM_TYPE_FLAG = [u8_ ;17usize ];
@@ -371,6 +375,7 @@ pub struct NV2080_CTRL_CMD_FB_GET_FB_REGION_FB_REGION_INFO {#[derive( Debug , Default , Copy , Clone )] pub struct NV2080_CTRL_CMD_FB_GET_FB_REGION_INFO_PARAMS {pub numFBRegions:u32_ , +pub __bindgen_padding_0: [u8 ;4usize ],pub fbRegion: [NV2080_CTRL_CMD_FB_GET_FB_REGION_FB_REGION_INFO ;16usize ], }#[repr( C )]
@@ -495,13 +500,16 @@ pub struct FW_WPR_LAYOUT_OFFSET {#[derive( Debug , Copy , Clone )] pub struct GspStaticConfigInfo_t {pub grCapsBits: [u8_ ;23usize ], +pub __bindgen_padding_0:u8 ,pub gidInfo:NV2080_CTRL_GPU_GET_GID_INFO_PARAMS ,pub SKUInfo:NV2080_CTRL_BIOS_GET_SKU_INFO_PARAMS , +pub __bindgen_padding_1: [u8 ;4usize ],pub fbRegionInfoParams:NV2080_CTRL_CMD_FB_GET_FB_REGION_INFO_PARAMS ,pub sriovCaps:NV0080_CTRL_GPU_GET_SRIOV_CAPS_PARAMS ,pub sriovMaxGfid:u32_ ,pub engineCaps: [u32_ ;3usize ],pub poisonFuseEnabled:u8_ , +pub __bindgen_padding_2: [u8 ;7usize ],pub fb_length:u64_ ,pub fbio_mask:u64_ ,pub fb_bus_width:u32_ ,
@@ -527,16 +535,20 @@ pub struct GspStaticConfigInfo_t { pub bIsMigSupported: u8_, pub RTD3GC6TotalBoardPower: u16_, pub RTD3GC6PerstDelay: u16_, + pub __bindgen_padding_3: [u8; 2usize], pub bar1PdeBase: u64_, pub bar2PdeBase: u64_, pub bVbiosValid: u8_, + pub __bindgen_padding_4: [u8; 3usize], pub vbiosSubVendor: u32_, pub vbiosSubDevice: u32_, pub bPageRetirementSupported: u8_, pub bSplitVasBetweenServerClientRm: u8_, pub bClRootportNeedsNosnoopWAR: u8_, + pub __bindgen_padding_5: u8, pub displaylessMaxHeads: VIRTUAL_DISPLAY_GET_NUM_HEADS_PARAMS, pub displaylessMaxResolution: VIRTUAL_DISPLAY_GET_MAX_RESOLUTION_PARAMS, + pub __bindgen_padding_6: [u8; 4usize], pub displaylessMaxPixels: u64_, pub hInternalClient: u32_, pub hInternalDevice: u32_,
Signature · 1 line
2.51.2
Alexandre Courbot
maintainerPATCH 2/4 gpu: nova-core: gsp: Fix length of received messages
In reply to Alexandre CourbotThe size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
--- drivers/gpu/nova-core/gsp/cmdq.rs | 11 +++++++---- drivers/gpu/nova-core/gsp/fw.rs | 2 +- 2 files changed, 8 insertions(+), 5 deletions(-)
drivers/gpu/nova-core/gsp/cmdq.rs +7 -4
@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), ); +// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >(); +// Check that the driver read area is large enough for the message. -if slice_1.len () + slice_2.len () < header.length () { +if slice_1.len () + slice_2.len () < msg_length {return Err (EIO ); }// Cut the message slices down to the actual length of the message. -let (slice_1, slice_2) =if slice_1.len () > header.length () { +let (slice_1, slice_2) =if slice_1.len () > msg_length {// PANIC: we checked above that `slice_1` is at least as long as `msg_header.length()`. - (slice_1.split_at (header.length ()).0 , &slice_2[0 ..0 ]) + (slice_1.split_at (msg_length).0 , &slice_2[0 ..0 ]) }else { ( slice_1,// PANIC: we checked above that `slice_1.len() + slice_2.len()` is at least as // large as `msg_header.length()`. - slice_2.split_at (header.length () - slice_1.len ()).0 , + slice_2.split_at (msg_length - slice_1.len ()).0 , ) };
drivers/gpu/nova-core/gsp/fw.rs +1 -1
@@ -853,7 +853,7 @@ pub(crate) fn set_checksum(&mut self, checksum: u32) { self.inner.checkSum = checksum; } -/// Returns the total length of the message. +/// Returns the total length of the message, message and RPC headers included. pub (crate )fn length (&self) ->usize {// `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of ::<Self >() -size_of ::<bindings::rpc_message_header_v >()
Signature · 1 line
2.51.2
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Hi Alex,
Quoted 18 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 5 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), ); +// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();
Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
thanks,
- Joel
Quoted 40 lines
drivers/gpu/nova-core/gsp/cmdq.rs +5
-4+// Check that the driver read area is large enough for the message. -if slice_1.len () + slice_2.len () < header.length () { +if slice_1.len () + slice_2.len () < msg_length {return Err (EIO ); }// Cut the message slices down to the actual length of the message. -let (slice_1, slice_2) =if slice_1.len () > header.length () { +let (slice_1, slice_2) =if slice_1.len () > msg_length {// PANIC: we checked above that `slice_1` is at least as long as `msg_header.length()`. - (slice_1.split_at (header.length ()).0 , &slice_2[0 ..0 ]) + (slice_1.split_at (msg_length).0 , &slice_2[0 ..0 ]) }else { ( slice_1,// PANIC: we checked above that `slice_1.len() + slice_2.len()` is at least as // large as `msg_header.length()`. - slice_2.split_at (header.length () - slice_1.len ()).0 , + slice_2.split_at (msg_length - slice_1.len ()).0 , ) };drivers/gpu/nova-core/gsp/fw.rs +1
-2@@ -853,7 +853,7 @@ pub(crate) fn set_checksum(&mut self, checksum: u32) { self.inner.checkSum = checksum; } -/// Returns the total length of the message. +/// Returns the total length of the message, message and RPC headers included. pub (crate )fn length (&self) ->usize {// `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of ::<Self >() -size_of ::<bindings::rpc_message_header_v >() --2.51.2
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Quoted 23 lines · Joel Fernandes
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );
Quoted 4 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
Would this be a possible use case for the untrusted data proposal
https://lwn.net/Articles/1034603/
?
Cheers
Dirk
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
On Dec 12, 2025, at 5:10 PM, Dirk Behme <[email protected]> wrote:
.12.25 08:59, Joel Fernandes wrote:
Hi Alex,
On Nov 22, 2025, at 12:00 AM, Alexandre Courbot <[email protected]> wrote:
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
---drivers/gpu/nova-core/gsp/cmdq.rs | 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs | 2 +-
2 files changed, 8 insertions(+), 5 deletions(-)
drivers/gpu/nova-core/gsp/cmdq.rs +2 -0
@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), ); +// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();
Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message. Show Quoted Content
On 12.12.25 08:59, Joel Fernandes wrote:
Hi Alex,
On Nov 22, 2025, at 12:00 AM, Alexandre Courbot <[email protected]> wrote:
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
---drivers/gpu/nova-core/gsp/cmdq.rs | 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs | 2 +-
2 files changed, 8 insertions(+), 5 deletions(-)
drivers/gpu/nova-core/gsp/cmdq.rs +2 -0
@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), ); +// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();
Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message. On 12.12.25 08:59, Joel Fernandes wrote:
Hi Alex,
On Nov 22, 2025, at 12:00 AM, Alexandre Courbot <[email protected]> wrote:
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
---drivers/gpu/nova-core/gsp/cmdq.rs | 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs | 2 +-
2 files changed, 8 insertions(+), 5 deletions(-)
drivers/gpu/nova-core/gsp/cmdq.rs +2 -0
@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), ); +// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();
Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
Would this be a possible use case for the untrusted data proposal
https://lwn.net/Articles/1034603/
Yeah, I think so. Thanks. What do you think Alex?
My opinion is that would be a larger/separate effort than what Alex is doing with this patch. But it sounds promising (I.e forcing validation of untrusted sources).
thanks,
- Joel
?
Cheers
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
In reply to Dirk BehmeOn 2025-12-12 at 19:10 +1100, Dirk Behme <[email protected]> wrote...
Quoted 24 lines · Joel Fernandes
Quoted 23 lines
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );
Quoted 4 lines
Quoted 4 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
I think we're guaranteed not to underflow here - check out the implementation for header.length():
/// Returns the total length of the message.
pub(crate) fn length(&self) -> usize {
// `rpc.length` includes the length of the GspRpcHeader but not the message header.
size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+ num::u32_as_usize(self.inner.rpc.length)
}So the above calculation expands to:
msg_length = size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+ num::u32_as_usize(self.inner.rpc.length) - size_of::<GspMsgElement>();
Where self.inner.rpc.length is guaranteed to be >= size_of::<rpc_message_header_v>() by the construction of the type.
Quoted 5 lines
Would this be a possible use case for the untrusted data proposal
https://lwn.net/Articles/1034603/
?
Responding here because Joel appears to have sent a HTML only response ;-)
I agree with Joel's points - this does sound useful but as a separate project. I'd imagine we'd want to it one layer lower though - ie. in the construction of the GspMsgElement.
Quoted 3 lines
Cheers
Dirk
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Hi Alistair,
Quoted 41 lines · Alistair Popple
On 2025-12-12 at 19:10 +1100, Dirk Behme <[email protected]> wrote...
Quoted 24 lines
Quoted 24 lines · Joel Fernandes
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );Quoted 4 lines
Quoted 4 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
I think we're guaranteed not to underflow here - check out the implementation for
header.length():/// Returns the total length of the message. pub(crate) fn length(&self) -> usize { // `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of::<Self>() - size_of::<bindings::rpc_message_header_v>() + num::u32_as_usize(self.inner.rpc.length) }
Quoted 6 lines
So the above calculation expands to:
msg_length= size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+num::u32_as_usize(self.inner.rpc.length)- size_of::<GspMsgElement>();Where self.inner.rpc.length is guaranteed to be >= size_of::<rpc_message_header_v>() by the construction of the type.
But this length field is coming from the firmware, correct? The guarantee is provided by firmware, not by Rust code calculating the length.
Maybe Rust validating that the length matches, or is greater than or equal to, the message header would be one way to avoid doing the checked subtraction. I would still be comfortable doing the checked subtraction in case the firmware payload in the message buffer is corrupted and the length field is corrupted.
I think Rust cannot trust fields coming from the firmware and needs to check them to prevent undefined behavior. Or maybe the policy is to include safety comments, like we do when expecting C code to behave in a certain way. I do not know. But we should identify the policy for this and stick to it for future such issues.
I think one way to verify that there is a Rust guarantee about the length field is to do the unchecked subtraction, compile the code, and then see if the generated code has any panics in it (With the overflow checking config enabled.)
If it does, then dead code elimination could not determine at compile time that the subtraction would not overflow. Right?
Quoted 8 lines
Quoted 6 lines
Would this be a possible use case for the untrusted data proposal
https://lwn.net/Articles/1034603/
?
Responding here because Joel appears to have sent a HTML only response ;-)
Sorry. :)
Quoted 4 lines
I agree with Joel's points - this does sound useful but as a separate project. I'd imagine we'd want to it one layer lower though - ie. in the construction of the GspMsgElement.
Agreed, thanks.
- Joel
Quoted 4 lines
Quoted 4 lines
Cheers
Dirk
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Quoted 6 lines · Joel Fernandes
Quoted 6 lines
On Dec 15, 2025, at 8:43 AM, Alistair Popple <[email protected]> wrote:... So the above calculation expands to:
msg_length= size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+num::u32_as_usize(self.inner.rpc.length)- size_of::<GspMsgElement>();
Quoted 7 lines
Quoted 1 line
Where self.inner.rpc.length is guaranteed to be >= size_of::<rpc_message_header_v>() by the construction of the type.
But this length field is coming from the firmware, correct? The guarantee is provided by firmware, not by Rust code calculating the length.
Maybe Rust validating that the length matches, or is greater than or equal to, the message header would be one way to avoid doing the checked subtraction. I would still be comfortable doing the checked subtraction in case the firmware payload in the message buffer is corrupted and the length field is corrupted.
I think Rust cannot trust fields coming from the firmware and needs to check them to prevent undefined behavior.
Right. The firmware is a separate code base, running on a separate processor, and it is not part of the Rust driver. So it cannot participate in any of the various Rust guarantees.
We should treat data that comes from the firmware as not yet validated, external data.
Or maybe the policy is to include safety comments, like we do when
expecting C code to behave in a certain way. I
do not know. But we should identify the policy for this and stick to it for future such issues.es
Yes. I've written above what I believe we should use for a policy.
thanks,
Signature · 1 line
John Hubbard
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Quoted 2 lines · John Hubbard
We should treat data that comes from the firmware as not yet validated, external data.
Maybe we should make it a policy that all data read from firmware / disk needs to be instantiate via a constructor that validates all the fields.
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Quoted 6 lines · Timur Tabi
Quoted 2 lines · John Hubbard
We should treat data that comes from the firmware as not yet validated, external data.
Maybe we should make it a policy that all data read from firmware / disk needs to be instantiate via a constructor that validates all the fields.
That's one approach, and maybe it will end up being the best and most desirable approach.
But I'd stop short of making it a full-blown policy, because there are other ways of validating the data that comes from the firmware, and there's not (yet?) any real need to require one particular solution, I think.
thanks,
Signature · 1 line
John Hubbard
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
In reply to Joel FernandesOn 2025-12-15 at 12:22 +1100, Joel Fernandes <[email protected]> wrote...
Quoted 43 lines
Hi Alistair,
Quoted 41 lines · Alistair Popple
On 2025-12-12 at 19:10 +1100, Dirk Behme <[email protected]> wrote...
Quoted 24 lines
Quoted 24 lines · Joel Fernandes
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );Quoted 4 lines
Quoted 4 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
I think we're guaranteed not to underflow here - check out the implementation for
header.length():/// Returns the total length of the message. pub(crate) fn length(&self) -> usize { // `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of::<Self>() - size_of::<bindings::rpc_message_header_v>() + num::u32_as_usize(self.inner.rpc.length) }
Quoted 8 lines
Quoted 6 lines
So the above calculation expands to:
msg_length= size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+num::u32_as_usize(self.inner.rpc.length)- size_of::<GspMsgElement>();Where self.inner.rpc.length is guaranteed to be >= size_of::<rpc_message_header_v>() by the construction of the type.
But this length field is coming from the firmware, correct? The guarantee is provided by firmware, not by Rust code calculating the length.
Oh you're right - I had this around the wrong way, I forgot our constructors were only used for creating messages not receiving them. Obviously killing time reading mailing lists in airports is not such a good idea :-)
Quoted 7 lines
Maybe Rust validating that the length matches, or is greater than or equal to, the message header would be one way to avoid doing the checked subtraction. I would still be comfortable doing the checked subtraction in case the firmware payload in the message buffer is corrupted and the length field is corrupted.
I think Rust cannot trust fields coming from the firmware and needs to check them to prevent undefined behavior. Or maybe the policy is to include safety comments, like we do when expecting C code to behave in a certain way. I do not know. But we should identify the policy for this and stick to it for future such issues.
I think one way to verify that there is a Rust guarantee about the length field is to do the unchecked subtraction, compile the code, and then see if the generated code has any panics in it (With the overflow checking config enabled.)
If it does, then dead code elimination could not determine at compile time that the subtraction would not overflow. Right?
Agreed. Whilst we can't avoid needing to trust the firmware at some level crashing the kernel in response to a bad message would be bad and make debugging it a pain.
Quoted 15 lines
Quoted 8 lines
Quoted 6 lines
Would this be a possible use case for the untrusted data proposal
https://lwn.net/Articles/1034603/
?
Responding here because Joel appears to have sent a HTML only response ;-)
Sorry. :)
Quoted 4 lines
I agree with Joel's points - this does sound useful but as a separate project. I'd imagine we'd want to it one layer lower though - ie. in the construction of the GspMsgElement.
So I guess we'd need our own implementation of a from_bytes trait or some such that would also validate the fields when deserialising the struct.
Quoted 10 lines
Agreed, thanks.
- Joel
Quoted 4 lines
Quoted 4 lines
Cheers
Dirk
Alexandre Courbot
maintainerRe: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
In reply to Alistair PoppleQuoted 39 lines · Alistair Popple
On 2025-12-12 at 19:10 +1100, Dirk Behme <[email protected]> wrote...
Quoted 24 lines · Joel Fernandes
Quoted 23 lines
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );Quoted 4 lines
Quoted 4 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
I think we're guaranteed not to underflow here - check out the implementation for
header.length():/// Returns the total length of the message. pub(crate) fn length(&self) -> usize { // `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of::<Self>() - size_of::<bindings::rpc_message_header_v>() + num::u32_as_usize(self.inner.rpc.length) }
Quoted 6 lines
So the above calculation expands to:
msg_length= size_of::<Self>() - size_of::<bindings::rpc_message_header_v>()
+num::u32_as_usize(self.inner.rpc.length)- size_of::<GspMsgElement>();Where self.inner.rpc.length is guaranteed to be >= size_of::<rpc_message_header_v>() by the construction of the type.
That's correct, although it defers the possibility of underflow to length, albeit using two constants. Still, doing this as a const would catch any potential issue at build-time:
pub(crate) fn length(&self) -> usize {
// `rpc.length` includes the length of the GspRpcHeader but not the message header.
const RPC_LENGTH: usize = size_of::<Self>() - size_of::<bindings::rpc_message_header_v>();
RPC_LENGTH + num::u32_as_usize(self.inner.rpc.length)
}This length computation has been the subject of debate between me and Alistair back when we were writing the code, so this part can be subject to change if doing so limits the amount of potentially panicking operations.
Quoted 5 lines
Quoted 5 lines
Would this be a possible use case for the untrusted data proposal
Quoted 7 lines
Quoted 1 line
?
Responding here because Joel appears to have sent a HTML only response ;-)
I agree with Joel's points - this does sound useful but as a separate project. I'd imagine we'd want to it one layer lower though - ie. in the construction of the GspMsgElement.
How would that be beneficial? We would need to use unsafe to access the data, but then unless we can encode the guarantees that we verified in the type itself (or its invariants, but that would quickly become cumbersome to manage) we would still have the same ops ongoing.
IMHO the simple and safe way is to use checked operations with data that comes from the GSP.
Re: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
In reply to Joel FernandesOn 2025-12-12 at 18:59 +1100, Joel Fernandes <[email protected]> wrote...
Quoted 23 lines
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();
Wouldn't it be better to add a new method to GspMsgElement to get the size of the associated message rather than open coding it here?
- Alistair
Quoted 48 lines
Is this immune to under flow without one of the checked subtraction wrappers? Either way, we should not tolerate the underflow I think. Which means it can panic when the rust overflow checks are enabled. Since the header length comes from firmware, this cannot be guaranteed to not underflow in the event of a malformed message.
thanks,
- Joel
Quoted 40 lines
drivers/gpu/nova-core/gsp/cmdq.rs +5
-4+// Check that the driver read area is large enough for the message. -if slice_1.len () + slice_2.len () < header.length () { +if slice_1.len () + slice_2.len () < msg_length {return Err (EIO ); }// Cut the message slices down to the actual length of the message. -let (slice_1, slice_2) =if slice_1.len () > header.length () { +let (slice_1, slice_2) =if slice_1.len () > msg_length {// PANIC: we checked above that `slice_1` is at least as long as `msg_header.length()`. - (slice_1.split_at (header.length ()).0 , &slice_2[0 ..0 ]) + (slice_1.split_at (msg_length).0 , &slice_2[0 ..0 ]) }else { ( slice_1,// PANIC: we checked above that `slice_1.len() + slice_2.len()` is at least as // large as `msg_header.length()`. - slice_2.split_at (header.length () - slice_1.len ()).0 , + slice_2.split_at (msg_length - slice_1.len ()).0 , ) };drivers/gpu/nova-core/gsp/fw.rs +1
-2@@ -853,7 +853,7 @@ pub(crate) fn set_checksum(&mut self, checksum: u32) { self.inner.checkSum = checksum; } -/// Returns the total length of the message. +/// Returns the total length of the message, message and RPC headers included. pub (crate )fn length (&self) ->usize {// `rpc.length` includes the length of the GspRpcHeader but not the message header. size_of ::<Self >() -size_of ::<bindings::rpc_message_header_v >() --2.51.2
Alexandre Courbot
maintainerRe: [PATCH 2/4] gpu: nova-core: gsp: Fix length of received messages
Quoted 24 lines · Alistair Popple
On 2025-12-12 at 18:59 +1100, Joel Fernandes <[email protected]> wrote...
Quoted 23 lines
Hi Alex,
Quoted 21 lines · Alexandre Courbot
The size of messages' payload is miscalculated, leading to extra data passed to the message handler. While this is not a problem with our current set of commands, others with a variable-length payload may misbehave. Fix this.
Signed-off-by Alexandre Courbot <[email protected]>---
drivers/gpu/nova-core/gsp/cmdq.rs| 11 +++++++----drivers/gpu/nova-core/gsp/fw.rs| 2 +-2 files changed, 8 insertions(+), 5 deletions(-)drivers/gpu/nova-core/gsp/cmdq.rs +0
-0@@ -588,21 +588,24 @@ fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { header.length(), );
Quoted 5 lines
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs fn wait_for_msg(&self, timeout: Delta) -> Result<GspMessage<'_>> { · line 592
Quoted 2 lines
drivers/gpu/nova-core/gsp/cmdq.rs +2
-0+// The length of the message that follows the header. +let msg_length = header.length () -size_of ::<GspMsgElement >();Wouldn't it be better to add a new method to GspMsgElement to get the size of the associated message rather than open coding it here?
Agreed, that seems to make sense and should provide us with a safe operation.
Alexandre Courbot
maintainerPATCH 3/4 gpu: nova-core: bindings: Derive `MaybeZeroable`
In reply to Alexandre CourbotCommit 4846300ba8f9 ("rust: derive Zeroable for all structs & unions generated by bindgen where possible") automatically derives MaybeZeroable for all bindings. This is better than selectively deriving Zeroable as it ensures all types that can implement Zeroable do.
Regenerate the nova-core bindings so they benefit from this, and remove a now unneeded implementation of Zeroable.
--- drivers/gpu/nova-core/gsp/fw.rs | 7 -- drivers/gpu/nova-core/gsp/fw/r570_144.rs | 11 ++- drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs | 93 ++++++++++++----------- 3 files changed, 54 insertions(+), 57 deletions(-)
drivers/gpu/nova-core/gsp/fw.rs +0 -7
@@ -797,13 +797,6 @@ fn init(cmd_size: usize, function: MsgFunction) -> impl Init<Self, Error> { } } -// SAFETY: We can't derive the Zeroable trait for this binding because the -// procedural macro doesn't support the syntax used by bindgen to create the -// __IncompleteArrayField types. So instead we implement it here, which is safe -// because these are explicitly padded structures only containing types for -// which any bit pattern, including all zeros, is valid. -unsafe impl Zeroable for bindings::rpc_message_header_v {} -/// GSP Message Element. /// /// This is essentially a message header expected to be followed by the message data.
drivers/gpu/nova-core/gsp/fw/r570_144.rs +7 -4
@@ -24,8 +24,11 @@ unreachable_pub, unsafe_op_in_unsafe_fn )] -use kernel::{ - ffi, - prelude::Zeroable ,// -}; +use kernel::ffi; +use pin_init::MaybeZeroable ; +include! ("r570_144/bindings.rs" ); + +// SAFETY: This type has a size of zero, so its inclusion into another type should not affect their +// ability to implement `Zeroable`. +unsafe impl <T > kernel::prelude::Zeroable for __IncompleteArrayField <T > {}
drivers/gpu/nova-core/gsp/fw/r570_144/bindings.rs +47 -46
360 lines not on this page · raw message
Signature · 1 line
2.51.2
Alexandre Courbot
maintainerPATCH 4/4 gpu: nova-core: gsp: Replace firmware version with "bindings" alias
In reply to Alexandre CourbotWe have an "bindings" alias to avoid having to mention the firmware version again and again, and limit the diff when upgrading the firmware. Use it where we neglected to.
--- drivers/gpu/nova-core/gsp/fw.rs | 58 ++++++++++++++++++++--------------------- 1 file changed, 29 insertions(+), 29 deletions(-)
drivers/gpu/nova-core/gsp/fw.rs +29 -29
@@ -141,8 +141,8 @@ unsafe impl AsBytes for GspFwWprMeta {}// are valid. unsafe impl FromBytes for GspFwWprMeta {} -type GspFwWprMetaBootResumeInfo = r570_144::GspFwWprMeta__bindgen_ty_1 ; -type GspFwWprMetaBootInfo = r570_144::GspFwWprMeta__bindgen_ty_1__bindgen_ty_1 ; +type GspFwWprMetaBootResumeInfo = bindings::GspFwWprMeta__bindgen_ty_1 ; +type GspFwWprMetaBootInfo = bindings::GspFwWprMeta__bindgen_ty_1__bindgen_ty_1 ;impl GspFwWprMeta {/// Fill in and return a `GspFwWprMeta` suitable for booting `gsp_firmware` using the
@@ -150,8 +150,8 @@ impl GspFwWprMeta {pub (crate )fn new (gsp_firmware: &GspFirmware , fb_layout: &FbLayout ) ->Self {Self (bindings::GspFwWprMeta {// CAST: we want to store the bits of `GSP_FW_WPR_META_MAGIC` unmodified. - magic: r570_144::GSP_FW_WPR_META_MAGIC as u64 , - revision: u64::from (r570_144::GSP_FW_WPR_META_REVISION ), + magic: bindings::GSP_FW_WPR_META_MAGIC as u64 , + revision: u64::from (bindings::GSP_FW_WPR_META_REVISION ), sysmemAddrOfRadix3Elf: gsp_firmware.radix3_dma_handle (), sizeOfRadix3Elf: u64::from_safe_cast (gsp_firmware.size), sysmemAddrOfBootloader: gsp_firmware.bootloader.ucode.dma_handle (),
@@ -315,19 +315,19 @@ fn from(value: MsgFunction) -> Self {#[repr( u32 )] pub (crate )enum SeqBufOpcode {// Core operation opcodes -CoreReset = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESET , -CoreResume = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESUME , -CoreStart = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_START , -CoreWaitForHalt = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_WAIT_FOR_HALT , +CoreReset = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESET , +CoreResume = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESUME , +CoreStart = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_START , +CoreWaitForHalt = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_WAIT_FOR_HALT ,// Delay opcode -DelayUs = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_DELAY_US , +DelayUs = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_DELAY_US ,// Register operation opcodes -RegModify = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_MODIFY , -RegPoll = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_POLL , -RegStore = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_STORE , -RegWrite = r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_WRITE , +RegModify = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_MODIFY , +RegPoll = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_POLL , +RegStore = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_STORE , +RegWrite = bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_WRITE , }impl fmt::Display for SeqBufOpcode {
@@ -351,25 +351,25 @@ impl TryFrom<u32> for SeqBufOpcode {fn try_from (value:u32 ) ->Result <SeqBufOpcode > {match value { - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESET => { + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESET => {Ok (SeqBufOpcode ::CoreReset ) } - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESUME => { + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_RESUME => {Ok (SeqBufOpcode ::CoreResume ) } - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_START => { + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_START => {Ok (SeqBufOpcode ::CoreStart ) } - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_WAIT_FOR_HALT => { + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_CORE_WAIT_FOR_HALT => {Ok (SeqBufOpcode ::CoreWaitForHalt ) } - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_DELAY_US =>Ok (SeqBufOpcode ::DelayUs ), - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_MODIFY => { + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_DELAY_US =>Ok (SeqBufOpcode ::DelayUs ), + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_MODIFY => {Ok (SeqBufOpcode ::RegModify ) } - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_POLL =>Ok (SeqBufOpcode ::RegPoll ), - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_STORE =>Ok (SeqBufOpcode ::RegStore ), - r570_144::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_WRITE =>Ok (SeqBufOpcode ::RegWrite ), + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_POLL =>Ok (SeqBufOpcode ::RegPoll ), + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_STORE =>Ok (SeqBufOpcode ::RegStore ), + bindings::GSP_SEQ_BUF_OPCODE_GSP_SEQ_BUF_OPCODE_REG_WRITE =>Ok (SeqBufOpcode ::RegWrite ), _ =>Err (EINVAL ), } }
@@ -385,7 +385,7 @@ fn from(value: SeqBufOpcode) -> Self {/// Wrapper for GSP sequencer register write payload. #[repr(transparent)] #[derive( Copy , Clone )] -pub (crate )struct RegWritePayload (r570_144::GSP_SEQ_BUF_PAYLOAD_REG_WRITE ); +pub (crate )struct RegWritePayload (bindings::GSP_SEQ_BUF_PAYLOAD_REG_WRITE );impl RegWritePayload {/// Returns the register address.
@@ -408,7 +408,7 @@ unsafe impl AsBytes for RegWritePayload {}/// Wrapper for GSP sequencer register modify payload. #[repr(transparent)] #[derive( Copy , Clone )] -pub (crate )struct RegModifyPayload (r570_144::GSP_SEQ_BUF_PAYLOAD_REG_MODIFY ); +pub (crate )struct RegModifyPayload (bindings::GSP_SEQ_BUF_PAYLOAD_REG_MODIFY );impl RegModifyPayload {/// Returns the register address.
@@ -436,7 +436,7 @@ unsafe impl AsBytes for RegModifyPayload {}/// Wrapper for GSP sequencer register poll payload. #[repr(transparent)] #[derive( Copy , Clone )] -pub (crate )struct RegPollPayload (r570_144::GSP_SEQ_BUF_PAYLOAD_REG_POLL ); +pub (crate )struct RegPollPayload (bindings::GSP_SEQ_BUF_PAYLOAD_REG_POLL );impl RegPollPayload {/// Returns the register address.
@@ -469,7 +469,7 @@ unsafe impl AsBytes for RegPollPayload {}/// Wrapper for GSP sequencer delay payload. #[repr(transparent)] #[derive( Copy , Clone )] -pub (crate )struct DelayUsPayload (r570_144::GSP_SEQ_BUF_PAYLOAD_DELAY_US ); +pub (crate )struct DelayUsPayload (bindings::GSP_SEQ_BUF_PAYLOAD_DELAY_US );impl DelayUsPayload {/// Returns the delay value in microseconds.
@@ -487,7 +487,7 @@ unsafe impl AsBytes for DelayUsPayload {}/// Wrapper for GSP sequencer register store payload. #[repr(transparent)] #[derive( Copy , Clone )] -pub (crate )struct RegStorePayload (r570_144::GSP_SEQ_BUF_PAYLOAD_REG_STORE ); +pub (crate )struct RegStorePayload (bindings::GSP_SEQ_BUF_PAYLOAD_REG_STORE );impl RegStorePayload {/// Returns the register address.
@@ -510,7 +510,7 @@ unsafe impl AsBytes for RegStorePayload {}/// Wrapper for GSP sequencer buffer command. #[repr(transparent)] -pub (crate )struct SequencerBufferCmd (r570_144::GSP_SEQUENCER_BUFFER_CMD ); +pub (crate )struct SequencerBufferCmd (bindings::GSP_SEQUENCER_BUFFER_CMD );impl SequencerBufferCmd {/// Returns the opcode as a `SeqBufOpcode` enum, or error if invalid.
@@ -612,7 +612,7 @@ unsafe impl AsBytes for SequencerBufferCmd {}/// Wrapper for GSP run CPU sequencer RPC. #[repr(transparent)] -pub (crate )struct RunCpuSequencer (r570_144::rpc_run_cpu_sequencer_v17_00 ); +pub (crate )struct RunCpuSequencer (bindings::rpc_run_cpu_sequencer_v17_00 );impl RunCpuSequencer {/// Returns the command index.
Signature · 1 line
2.51.2
Alexandre Courbot
maintainerQuoted 13 lines · Alexandre Courbot
This series contains a few fixups for the recently merged GSP command-queue code, by order of importance:
- Some explicit padding required to safely implement
AsByteswas missing in the bindings,
- A bug in the received message length calculation results in the message handler being given more data than it should,
-MaybeZeroableis now derived by the kernel's bindgen, but the Nova bindings have not been updated for that,
- Some items in the bindings were referred to using the version module directly, instead of the alias we defined to limit the diff when we upgrade firmware versions.
Quoted 3 lines
All of them address "bugs" (with the first two fixing actual correctness issues), but since Nova does not do much anyway, they are also not absolutely critical and can wait -rc1 if we prefer to do so.
These patches are missing "Fixes:" tags - will send a v2 with them.