Re: [PATCH 1/2] target/arm: Log M-profile vector table accesses

2022-03-16 Thread Alex Bennée
Peter Maydell writes: > Currently the CPU_LOG_INT logging misses some useful information > about loads from the vector table. Add logging where we load vector > table entries. This is particularly helpful for cases where the user > has accidentally not put a vector table in their image at all

Re: [PATCH 1/2] target/arm: Log M-profile vector table accesses

2022-03-15 Thread Richard Henderson
On 3/15/22 13:43, Peter Maydell wrote: Currently the CPU_LOG_INT logging misses some useful information about loads from the vector table. Add logging where we load vector table entries. This is particularly helpful for cases where the user has accidentally not put a vector table in their image

[PATCH 1/2] target/arm: Log M-profile vector table accesses

2022-03-15 Thread Peter Maydell
Currently the CPU_LOG_INT logging misses some useful information about loads from the vector table. Add logging where we load vector table entries. This is particularly helpful for cases where the user has accidentally not put a vector table in their image at all, which can result in confusing gu