On Tue, Apr 30, 2024 at 01:00:57PM +0800, Yi Liu wrote: > > There is nothing to do about this race, but lets note it and say the > > concurrent PRI path will eventually become consistent and there is no > > harm in directing PRI to the wrong domain. > > If the old and new domain points to the same address space, it is fine. > How about they point to different address spaces? Delivering the PRI to > new domain seems problematic. Or, do we allow such domain replacement > when there is still ongoing DMA? New PRI could happen an instant later and hit the new domain, or an instant before and hit the old domain. It is fine > > Let's also check that receiving a PRI on a domain that is not PRI > > capable doesn't explode in case someone uses replace to change from a > > PRI to non PRI domain. > > Just need to refuse the receiving PRI, is it? Yes > BTW. Should the PRI cap > be disabled in the devices side and the translation structure (e.g. > PRI enable bit in pasid entry) when the replacement is done? Yes, after domain attachment completes Jason
