• State Accepted Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 89 subscribers
  • Views 3769 views
  • Users 0 members are here
Options
Related
How was your experience today?
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

MPAM cache partitioning support in FVP base model

Matteo Zini

Hello,


I was trying to configure the MPAM system for cache capacity partitioning utilising the fvp base model. I noticed, reading the comments related to the configuration parameters, that the maximum capacity control is not functional, but, anyway, the registers are available.
However, the MPAM reference manual specifies that, in the CMAX field of the MPAMCFG_CMAX register, only n bits are implemented, where n is found reading the CMAX_WD of the MPAMF_CMAX_IDR register. The implemented bits should be the n most significant bits, as specified at page 11-209:


[...]
The implemented width of the fixed-point fraction is given in MPAMF_CCAP_IDR.CMAX_WD.
Unimplemented bits within the field are RAZ/WI. The implemented bits of the CMAX field are always the most-significant bits of the field.
[...]


After some test, instead, it looks like the implemented bits are in reality the least significant ones. In fact, if we set for example 8 bits for the CMAX_WD parameter in the configuration and we try to write 0x1234 in the register, accessing it again we can read 0x34 and not 0x1200 as expected.
Is this the correct behaviour or there is something more that I'm missing?
Moreover, I wanted to ask if there is the possibility that this functionality, as well as the other unimplemented types of control, will be integrated in an FVP model in the future.

Thank you and regards.
Matteo Zini

Parents
  • 0

    Hi Matteo, I realize that I didn't completely close the loop on the previous MPAM discussion.  to implement MPAM in a system, it needs to be supported across multiple components, including the interconnect and memory controller.  that is not the case on the Base FVP.   This means that you can have in-cluster MPAM (i.e., within the CPU cluster) but not system wide on the Base FVP.  Is that sufficient for your investigations?

    To answer the question around future FVP plans, we do have an FVP that support MPAM but it is only available to partners that have an NDA in place as it contains IP that is not yet public.

Reply
  • 0

    Hi Matteo, I realize that I didn't completely close the loop on the previous MPAM discussion.  to implement MPAM in a system, it needs to be supported across multiple components, including the interconnect and memory controller.  that is not the case on the Base FVP.   This means that you can have in-cluster MPAM (i.e., within the CPU cluster) but not system wide on the Base FVP.  Is that sufficient for your investigations?

    To answer the question around future FVP plans, we do have an FVP that support MPAM but it is only available to partners that have an NDA in place as it contains IP that is not yet public.

Children