Re: target/arm: cp15.dacr migration

2022-02-08 Thread Peter Maydell
On Tue, 8 Feb 2022 at 04:56, Pavel Dovgalyuk wrote: > > On 07.02.2022 16:44, Peter Maydell wrote: > > On Mon, 7 Feb 2022 at 12:13, Pavel Dovgalyuk > > wrote: > >> > >> I recently encountered a problem with cp15.dacr register. > >> It has _s and _ns versions. During the migration only dacr_ns is

Re: target/arm: cp15.dacr migration

2022-02-07 Thread Pavel Dovgalyuk
On 07.02.2022 16:44, Peter Maydell wrote: On Mon, 7 Feb 2022 at 12:13, Pavel Dovgalyuk wrote: I recently encountered a problem with cp15.dacr register. It has _s and _ns versions. During the migration only dacr_ns is saved/loaded. But both of the values are used in get_phys_addr_v5 and

Re: target/arm: cp15.dacr migration

2022-02-07 Thread Peter Maydell
On Mon, 7 Feb 2022 at 12:13, Pavel Dovgalyuk wrote: > > I recently encountered a problem with cp15.dacr register. > It has _s and _ns versions. During the migration only dacr_ns is > saved/loaded. > But both of the values are used in get_phys_addr_v5 and get_phys_addr_v6 > functions. Therefore VM

target/arm: cp15.dacr migration

2022-02-07 Thread Pavel Dovgalyuk
I recently encountered a problem with cp15.dacr register. It has _s and _ns versions. During the migration only dacr_ns is saved/loaded. But both of the values are used in get_phys_addr_v5 and get_phys_addr_v6 functions. Therefore VM behavior becomes incorrect after loading the vmstate. I