This repository was archived by the owner on Nov 28, 2022. It is now read-only.

Description
Because RMD should not cache/store any resctrl information, RMD should throw error if user unmount resctrl
Here are 2 cases where RMD should have responded to an error but did not
A. GET /workloads
- Run RMD in a fresh environment, there is no workload/COS in RMD/resctrl
- Create a workload via POST /workloads
- umount resctrl
- Query workloads via GET /workloads,
and then you'll see that the response includes the workload you just created
B. GET /cache/l3
- Run RMD in a fresh environment, there is no workload/COS in RMD/resctrl
- Query cache information via GET /cache/l3
- umount resctrl
- Query cache information via GET /cache/l3,
and then you'll get a response includes cache information without any Internal Server Error.