[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: qemu: fatal: lockup...
From: |
Peter Maydell |
Subject: |
Re: qemu: fatal: lockup... |
Date: |
Tue, 7 Dec 2021 10:12:06 +0000 |
On Tue, 7 Dec 2021 at 09:23, abhijeet inamdar
<abhijeetinamdar3005@gmail.com> wrote:
>
> And we have two memory map one at the boot time and other is the normal
> memory map. There is slight chance in the size/addresses. My doubt is which
> do mapping do we usually follow?
The rule of thumb is: model what the real hardware does.
If that means "we have one mapping at boot time and then
at runtime there's some register that changes the mapping",
then model that.
That said, sometimes if the two maps are very similar, or if
in fact you know the guest you care about never does whatever
the thing is to change the memory map, then you can get away
with only modelling one of them.
-- PMM
- qemu: fatal: lockup..., abhijeet inamdar, 2021/12/04
- Re: qemu: fatal: lockup..., Peter Maydell, 2021/12/05
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/05
- Re: qemu: fatal: lockup..., Peter Maydell, 2021/12/06
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/06
- Re: qemu: fatal: lockup..., Peter Maydell, 2021/12/06
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/06
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/07
- Re: qemu: fatal: lockup...,
Peter Maydell <=
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/07
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/08
- Re: qemu: fatal: lockup..., Peter Maydell, 2021/12/08
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/08
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/08
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/10
- Re: qemu: fatal: lockup..., Peter Maydell, 2021/12/10
- Re: qemu: fatal: lockup..., abhijeet inamdar, 2021/12/14