Originally memory access logs were a debug define that then were converted to log messages but were classified as guest_errors which already logs misc errors. As invalid memory access logs can come from accessing not emulated peripherals or memory areas, these often generate a lot of messages that are better be controlled separately from other errors to avoid obscuring those. As an example try 'qemu-system-ppc -d guest_errors' to see the problem. After this series the actual guest error logs are easier to spot. I've tried to submit this before but there were some people who liked the current behaviour so now this series has another patch that preserves the old optino printing a warning to allow time to get used to the new behaviour (which actually brings back the old behaviour when mem access logs were a debug define).
Regards, BALATON Zoltan BALATON Zoltan (2): log: Add separate debug option for logging invalid memory accesses log: Suggest using -d guest_error,memaccess instead of guest_errors docs/devel/secure-coding-practices.rst | 2 +- include/qemu/log.h | 1 + system/memory.c | 6 +++--- system/physmem.c | 2 +- tests/avocado/smmu.py | 2 +- tests/qtest/pnv-host-i2c-test.c | 2 +- util/log.c | 8 +++++++- 7 files changed, 15 insertions(+), 8 deletions(-) -- 2.30.9
