Re: [PATCH v3 33/39] xen/riscv: restore register state in the new IMSIC VS-file

[Baptiste Le Duc <baptiste.le-duc@xxxxxxxxxx>]

On 2026-11-06 11:04 +0100, Oleksii Kurochko wrote:
> [ ... 13 lines skipped ... ]
> I don't think it's needed. The barrier is there so that nothing gets
> lost from the old file: once the extempore MSI sent to the hart of the
> old file has arrived, every MSI the APLIC sent towards the old file
> before the retargeting has landed there, so what's read out of the old
> file is complete.
> 
> MSIs sent after the retargeting go to the new file, and they can keep
> arriving at any time, including while the saved state is being
> restored, so an extempore MSI to the hart of the new file wouldn't stop
> them anyway: it would only tell that the MSIs sent before it have
> arrived. That's why the saved eip/eie bits are ORed into the new file
> rather than written to it, so that whatever lands there in the meantime
> is kept, and why eidelivery is restored last, so that the new file
> doesn't deliver anything until its state is complete.
> 
Ok it's more clear thanks!

-- 
Baptiste Le Duc <baptiste.le-duc@xxxxxxxxxx>