Hey Marc, On Thu, Mar 30, 2023 at 11:04:18AM +0100, Marc Zyngier wrote: > When taking an exception between the EL1&0 translation regime and > the EL2 translation regime, the page table walker is allowed to > complete the walks started from EL0 or EL1 while running at EL2. > > It means that altering the system registers that define the EL1&0 > translation regime is fraught with danger *unless* we wait for > the completion of such walk with a DSB (R_LFHQG and subsequent > statements in the ARM ARM). We already did the right thing for > other external agents (SPE, TRBE), but not the PTW. > > In the case of nVHE, this is a bit involved, as there are a number > of situations where this can happen (such as switching between > host and guest, invalidating TLBs...). I'm assuming that the dsb(ishst) done in some of the other TLB invalidation handlers is sufficient, as R_LFHQG does not describe the scope of the DSB (i.e. loads and/or stores). Nonetheless, short of any special serialization rules, it seems probable for the PTW to have both outstanding loads and stores. Is there some other language in the architecture that speaks to the effects of _any_ DSB on the PTW? I couldn't find it myself. In any case, I'll have to take you at your word if you say it is sufficient :) -- Thanks, Oliver
