Re: [PATCH v2 03/11] target/arm: ensure HVF traps set appropriate MemTxAttrs

On 26.09.22 15:38, Alex Bennée wrote: As most HVF devices are done purely in software we need to make sure we properly encode the source CPU in MemTxAttrs. This will allow the device emulations to use those attributes rather than relying on current_cpu (although current_cpu will still be correc

Re: [PATCH v2 03/11] target/arm: ensure HVF traps set appropriate MemTxAttrs

Peter Maydell writes: > On Mon, 26 Sept 2022 at 14:39, Alex Bennée wrote: >> >> As most HVF devices are done purely in software we need to make sure >> we properly encode the source CPU in MemTxAttrs. This will allow the >> device emulations to use those attributes rather than relying on >> cu

Re: [PATCH v2 03/11] target/arm: ensure HVF traps set appropriate MemTxAttrs

On Mon, 26 Sept 2022 at 14:39, Alex Bennée wrote: > > As most HVF devices are done purely in software we need to make sure > we properly encode the source CPU in MemTxAttrs. This will allow the > device emulations to use those attributes rather than relying on > current_cpu (although current_cpu w

[PATCH v2 03/11] target/arm: ensure HVF traps set appropriate MemTxAttrs

As most HVF devices are done purely in software we need to make sure we properly encode the source CPU in MemTxAttrs. This will allow the device emulations to use those attributes rather than relying on current_cpu (although current_cpu will still be correct in this case). Signed-off-by: Alex Benn