Change Details

Add the last stage 2 pte fields and use them to create the stage 2 maps. When creating these we need to clean the D-cache to the point of coherency so any data in them is visible to any newly created guest OS. We also need to invalidate the I-cache when creating executable entries, however to simplify this delay the invalidation until the guest executes this memory. This allows userspace to load code into a hypervisor guest, perform its own clean operation, then have the kernel invalidate the I-cache as needed. This also allows us to clean a VPIPT I-cache as it needs to be performed at EL2, however this is as yet unimplemented.

Add minimal support for creating stage 2 IPA -> PA mappings. For this we need to: * Create a new vmid set to allocate a vmid for each Virtual Machine * Add the missing stage 2 attributes * Use these in pmap_enter to create a new mapping * Handle stage 2 faults The vmid set is based on the current asid set that was generalised in r358328. It adds a function pointer for bhyve to use when the kernel needs to reset the vmid set. This will need to call into EL2 and invalidate the TLB. The stage 2 attributes have been added. To simplify setting these fields two new functions are added to get the memory type and protection fields. These are slightly different on stage 1 and stage 2 tables. We then use them in pmap_enter to set the new level 3 entry to be stored. The D-cache on all entries is cleaned to the point of coherency. This is to allow the data to be visible to the VM. To allow for userspace to load code when creating a new executable entry an invalid entry is created. When the VM tried to use it the I-cache is invalidated. As the D-cache has already been cleaned this will ensure the I-cache is synchronised with the D-cache. When the hardware implements a VPIPT I-cache we need to either have the correct VMID set or invalidate it from EL2. As the host kernel will have the wrong VMID set we need to call into EL2 to clean it. For this a second function pointer is added that is called when this invalidation is needed.

Add the last stage 2 pte fields and use them to create the stage 2 maps.minimal support for creating stage 2 IPA -> PA mappings. For this When creating these we need to clean the D-cache to the point of coherencyto: so any data in them is visible to any newly created guest OS. * Create a new vmid set to allocate a vmid for each Virtual Machine * Add the missing stage 2 attributes * Use these in pmap_enter to create a new mapping * Handle stage 2 faults We also need to invalidateThe vmid set is based on the I-cache when creating executable entries,current asid set that was generalised in r358328. however to simplify this delay the invalidation until the guest executesIt adds a function pointer for bhyve to use when the kernel needs to reset the this memoryvmid set. This will need to call into EL2 and invalidate the TLB. The stage 2 attributes have been added. This allows userspace to load code into a hypervisor guest,To simplify setting these fields two new perform its own clean operafunctions are added to get the memory type and protection, fields. then have the kernel invalidate theThese are slightly I-cache as neededdifferent on stage 1 and stage 2 tables. This also allows us to clean a VPIPT I-cache as itWe then use them in pmap_enter to set the needs to be performed at EL2,w level 3 entry to be stored. The D-cache on all entries is cleaned to the point of coherency. This is to allow the data to be visible to the VM. To allow for userspace to load code when creating a new executable entry an invalid entry is created. When the VM tried to use it the I-cache is invalidated. As the D-cache has already been cleaned this will ensure the I-cache is synchronised with the D-cache. When the hardware implements a VPIPT I-cache we need to either have the correct VMID set or invalidate it from EL2. As the host kernel will have the wrong VMID set we need to call into EL2 to clean it. however this is as yet unimplementedFor this a second function pointer is added that is called when this invalidation is needed.