>> +enum resctrl_scope {
>> + RESCTRL_L3_CACHE,
>> + RESCTRL_L2_CACHE,
>> +};
>
> How about?
>
> enum resctrl_scope {
> RESCTRL_L2_CACHE = 2,
> RESCTRL_L3_CACHE,
> };
Babu. Thanks for the review.
Reinette made the same observation. I'm updating the
patch to do this. With small extra defensive step to explicitly define
RESCTRL_L3_CACHE = 3,
rather than relying on the compiler picking the next integer ... just in
case somebody adds another enum between the L2 and L3 lines.
-Tony
