Re: [Qemu-devel] [PATCH 10/15] target/arm: Don't use cpsr_write/cpsr_read to transfer M profile XPSR

2017-08-04 Thread Peter Maydell
On 3 August 2017 at 23:13, Richard Henderson wrote: > On 08/02/2017 09:43 AM, Peter Maydell wrote: >> +if (val & XPSR_EXCP) { >> +/* This is a CPSR format value from an older QEMU. (We can tell >> + * because values transferred in XPSR format always have zero >> +

Re: [Qemu-devel] [PATCH 10/15] target/arm: Don't use cpsr_write/cpsr_read to transfer M profile XPSR

2017-08-03 Thread Richard Henderson
On 08/03/2017 03:13 PM, Richard Henderson wrote: > On 08/02/2017 09:43 AM, Peter Maydell wrote: >> +if (val & XPSR_EXCP) { >> +/* This is a CPSR format value from an older QEMU. (We can tell >> + * because values transferred in XPSR format always have zero >> +

Re: [Qemu-devel] [PATCH 10/15] target/arm: Don't use cpsr_write/cpsr_read to transfer M profile XPSR

2017-08-03 Thread Richard Henderson
On 08/02/2017 09:43 AM, Peter Maydell wrote: > +if (val & XPSR_EXCP) { > +/* This is a CPSR format value from an older QEMU. (We can tell > + * because values transferred in XPSR format always have zero > + * for the EXCP field, and CPSR format will alway

[Qemu-devel] [PATCH 10/15] target/arm: Don't use cpsr_write/cpsr_read to transfer M profile XPSR

2017-08-02 Thread Peter Maydell
For M profile the XPSR is a similar but not identical format to the A profile CPSR/SPSR. (For instance the Thumb bit is in a different place.) For guest accesses we make the M profile code go through xpsr_read() and xpsr_write() which handle the different layout. However for migration we use cpsr_r