Skip to content

image: include /driver/cpu/amd/zen in cpio for dramtest #190

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jclulow
Copy link
Collaborator

@jclulow jclulow commented Feb 27, 2025

As part of building a new image for the DRAM testing station in manufacturing, I have rebased the dramtest branch of illumos on top of the latest stlouis bits. The code in the branch essentially blocks forever in the boot_image module, loads the zen_umc module, and prints out information about the DIMMs in the machine over and over. The manufacturing software knows how to interpret this data (by watching the console) to produce a report.

It would appear that the last time I built the image for this purpose, I was (somehow) including the zen_umc module and other parts of the /driver/cpu/amd/zen package in the cpio archive. It's possible that part of making the image ready for production involved trimming those files out.

The files are not strictly necessary in the regular image, but they also only increase the size of the compressed cpio archive from 8.22MB to 8.27MB. It doesn't seem worth adding complexity to make them optional here, given the small size.

@@ -206,6 +210,7 @@ kernel/misc/amd64/sha2
kernel/misc/amd64/skein
kernel/misc/amd64/strplumb
kernel/misc/amd64/tlimod
kernel/misc/amd64/zen_data
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you need zen_data? As far as I know this just provides pin data for zen_gpio

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have no idea! I just included everything that isn't a manual page haha. I will investigate though.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this isn't required.

@rmustacc
Copy link
Contributor

The files are not strictly necessary in the regular image, but they also only increase the size of the compressed cpio archive from 8.22MB to 8.27MB. It doesn't seem worth adding complexity to make them optional here, given the small size.

When we move to a minibar enabled world and have a NIC present (which I appreciate will not be for some time) can we then move to using a normal full boot image and not need to rely on this exceptionally private interface? At which point we will no longer need the subset of things here and would be able to remove the partial contents of this package?

@jclulow
Copy link
Collaborator Author

jclulow commented Feb 28, 2025

When we move to a minibar enabled world and have a NIC present (which I appreciate will not be for some time) can we then move to using a normal full boot image and not need to rely on this exceptionally private interface? At which point we will no longer need the subset of things here and would be able to remove the partial contents of this package?

Sure! If someone wants to shove a PCIe NIC into the sharkfin slot on the board I suspect that would also work! The challenge has been that we do this prior to assembly in the chassis. If either of these are true, we can certainly stop doing this:

  • minibar works with a pre-assembly chassis and we can use it for the DIMM test station
  • we stop doing the pre-assembly DRAM test, and just move DRAM checks into the regular programming flow

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.

3 participants