2) As I said above, what you show is not the effective mask used by theÂguest
Why would a sysfs attribute for the mediated matrix device show the effective
maskÂusedÂbyÂtheÂguest?
OK,ÂbadÂword,Â"effective",ÂreplaceÂwithÂ"really".
WeÂdoÂnotÂimplementÂanyÂkindÂofÂprovisioningÂnorÂdoÂweÂimplementÂupdate
ofÂtheÂCRYCBÂatÂanyÂpointÂafterÂtheÂfirstÂmediatedÂdeviceÂopen.
IÂthinkÂthisÂisÂaÂwayÂweÂmightÂbeÂableÂtoÂhotÂplug/unplugÂdevices.
Binding a queue and updating the mask can be done at any time (may be weÂshouldÂchangeÂthisÂ?)
As I said above, I think we can utilize this as a means of hot plugging/unpluggingÂAP
adapters and domains. If the guest is running when an adapter or domain isÂassigned,
weÂcanÂupdateÂtheÂguest'sÂCRYCBÂatÂthatÂtime.
What is the point of showing a matrix which will never be used by the guest?
ThatÂisÂsimplyÂnotÂtrue.ÂTheÂmatrixÂWILLÂbeÂusedÂbyÂaÂguestÂtheÂnextÂtimeÂa
guestÂisÂconfiguredÂwithÂaÂvfio-apÂdeviceÂreferencingÂtheÂpathÂtoÂthe
mediatedÂmatrixÂdeviceÂ-Âi.e.,Â-deviceÂvfio-ap,sysfsdev=$PATH.ÂTheÂpoint
is to show the matrix assigned to the mediated matrix device. In my mind,Âthe
mediatedÂmatrixÂdeviceÂisÂaÂseparateÂobjectÂfromÂtheÂguest.ÂSureÂitÂisÂused
to configure a guest's matrix when the guest is started, but it could be used
toÂconfigureÂtheÂmatrixÂforÂanyÂguest;ÂitÂhasÂnoÂdirectÂconnectionÂtoÂa
particularÂguestÂuntilÂaÂguestÂusingÂtheÂdeviceÂisÂstarted.ÂIMHOÂtheÂsysfs
attributesÂforÂtheÂmediatedÂmatrixÂdeviceÂreflectÂonlyÂtheÂattributesÂof
theÂdevice,ÂnotÂtheÂattributesÂofÂaÂguest.