On Mon, Mar 03, 2025 at 03:21:57PM +0000, Shameerali Kolothum Thodi wrote: > I am working on the above now and have quick question to you😊. > > Looking at the smmu_dev_attach_viommu() fn here[0], > it appears to do the following: > > 1. Alloc a s2_hwpt if not allocated already and attach it. > 2. Allocate abort and bypass hwpt > 3. Attach bypass hwpt. > > I didn't get why we are doing the step 3 here. To me it looks like, > when we attach the s2_hwpt(ie, the nested parent domain attach), > the kernel will do, > > arm_smmu_attach_dev() > arm_smmu_make_s2_domain_ste() > > It appears through step 3, we achieve the same thing again. > > Or it is possible I missed something obvious here.
Because a device cannot attach to a vIOMMU object directly, but only via a proxy hwpt_nested. So, this bypass hwpt gives us the port to associate the device to the vIOMMU, before a vDEVICE or a "translate" hwpt_nested is allocated. Currently it's the same because an S2 parent hwpt holds a VMID, so we could just attach the device to the S2 hwpt for the same STE configuration as attaching the device to the proxy bypass hwpt. Yet, this will change in the future after letting vIOMMU objects hold their own VMIDs to share a common S2 parent hwpt that won't have a VMID, i.e. arm_smmu_make_s2_domain_ste() will need the vIOMMU object to get the VMID for STE. I should have added a few lines of comments there :) Thanks Nicolin
