Skip to content
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

Does PLCT-GEM5 support saving checkpoint of vector registers? #17

Open
LandonWong opened this issue Oct 26, 2022 · 2 comments
Open

Does PLCT-GEM5 support saving checkpoint of vector registers? #17

LandonWong opened this issue Oct 26, 2022 · 2 comments

Comments

@LandonWong
Copy link

Does plct-gem5 support saving and restoring vector registers in checkpoint? If supported, in which file are the changes made?

Thanks,

@huxuan0307
Copy link
Contributor

I'm sorry that I have no idea about how to use checkpoints in gem5 right now. Maybe you can try to save and restore risc-v checkpoint on non-vector workloads. And then, use the same way to save and restore checkpoint on vector workloads. I will figure out checkpoints in a few weeks.

@LandonWong
Copy link
Author

Thanks. In gem5 SE mode, we can save and restore the current state of CPU and memory to *.cpt (CPU state) and *.pmem (Memory contents). Where *.cpt contains values of general purpose registers, float registers and vector registers (none now).
I think it may need some efforts to support saving and restoring vector registers: porting that logic to the PLCT rvv CPU model (x86 and arm already realized vector checkpoint).
I would appreciate it if you could share with me if there are plans to support it, many thanks!

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

No branches or pull requests

2 participants