1. Messages
  2. CAT definition in the scenario xmls

Re: CAT definition in the scenario xmls

Geoffroy Van Cutsem
 

I’d love to see that being added to our code, would you care to develop and patch and submit it upstream? 😉

 

Thanks!
Geoffroy

 

From: acrn-users@... <acrn-users@...> On Behalf Of Minggui Cao
Sent: Saturday, April 2, 2022 2:04 am
To: acrn-users@...
Subject: Re: [acrn-users] CAT definition in the scenario xmls

 

Yes, correct.

 

You can add your code in function: setup_clos

 

There is a data structure: res_cap_info, if possible, you also can re-use it to configure your L2 CAT.

 

Thanks

Minggui

 

From: acrn-users@... <acrn-users@...> On Behalf Of jordan.nowak22@...
Sent: Friday, April 1, 2022 2:54 PM
To: acrn-users@...
Subject: Re: [acrn-users] CAT definition in the scenario xmls

 

Yes i already tested on ACRN console, what i'm trying to achieve is a permanent configuration

When you say RDT code. do you mean this below path to code?
hypervisor/arch/x86/rdt.c
Join acrn-users@lists.projectacrn.org to automatically receive all group messages.