Skip to content

mctpd: update supports_vdm check#141

Merged
jk-ozlabs merged 5 commits intoCodeConstruct:mainfrom
msnidhin:vdmMsgTypes
Mar 4, 2026
Merged

mctpd: update supports_vdm check#141
jk-ozlabs merged 5 commits intoCodeConstruct:mainfrom
msnidhin:vdmMsgTypes

Conversation

@Ruta01
Copy link
Contributor

@Ruta01 Ruta01 commented Mar 3, 2026

supports_vdm check to be decided based on supported PCIE/IANA message type instead of formatID.
Fixes: cb182be ("mctpd: Add VendorDefinedMessageTypes property")

@jk-ozlabs
Copy link
Member

Looks good - just a formatting failure in CI.

@jk-ozlabs
Copy link
Member

Also, you may want to check you git author/commiter settings; it looks like you have a username there instead of a full name.

Perhaps:

git config --global user.name "Ruta Abhyankar"

- but if the rutaabhyankar format is inetentional, that's OK too.

@jk-ozlabs
Copy link
Member

Thanks for the update. The failing test is due to the actual bug; I have some testcase changes that I will include in the merge.

@Ruta01
Copy link
Contributor Author

Ruta01 commented Mar 4, 2026

Thanks for the update. The failing test is due to the actual bug; I have some testcase changes that I will include in the merge.

I updated the test. Looks like some format issue in test file. Will check.

@jk-ozlabs
Copy link
Member

Don't worry about the test changes: I have some reworks done on how the VDM types are handled within the Endpoint code, which I will merge alongside your change.

Might be helpful to add a Fixes line to your commit though:

Fixes: cb182be ("mctpd: Add VendorDefinedMessageTypes property")

@jk-ozlabs
Copy link
Member

This still has the testcase changes though.

@jk-ozlabs
Copy link
Member

OK, I have pushed your branch to my full set of changes (including your fix, and a test for this case). Please let me know if that looks OK to you.

@Ruta01
Copy link
Contributor Author

Ruta01 commented Mar 4, 2026

Looks good. I think we can merge it.

jk-ozlabs and others added 5 commits March 4, 2026 20:21
Rather than dealing with lists of numbers, provide a proper class for a
VDM type, including a serialiser for Get Vendor Message Type support
responses.

Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Currently, we use a default [0] for our types list, but do not inspect
the vdm types to augment with 7e/7f.

Use the provided VDM types to also populate the base types by default,
but still allow an explicit types argument to override.

Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
…comparisons

Now that we have a VDM type, construct a set from dbus responses, and
use this to copmpare against expected values.

Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
Updated supports_vdm check to be decided based on supported
PCIE/IANA message type instead of formatID.

[Minor commit message changes from Jeremy Kerr]

Fixes: cb182be ("mctpd: Add VendorDefinedMessageTypes property")
Signed-off-by: rutaabhyankar <ruta.abhyankar@intel.com>
Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
We have a bug where the presence of the control type will trigger a VDM
query, rather than 7e/7f.

Explicitly clear the types set, to check for this case.

Signed-off-by: Jeremy Kerr <jk@codeconstruct.com.au>
@jk-ozlabs jk-ozlabs merged commit 0340102 into CodeConstruct:main Mar 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants