|
From: | Alexander Graf |
Subject: | Re: [Qemu-devel] [PATCH v3] qemu-log: add log category for MMU info |
Date: | Mon, 03 Nov 2014 16:05:19 +0100 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 |
On 29.10.14 06:37, Antony Pavlov wrote: > Running barebox on qemu-system-mips* with '-d unimp' overloads > stderr by very very many mips_cpu_handle_mmu_fault() messages: > > mips_cpu_handle_mmu_fault address=b80003fd ret 0 physical 00000000180003fd > prot 3 > mips_cpu_handle_mmu_fault address=a0800884 ret 0 physical 0000000000800884 > prot 3 > mips_cpu_handle_mmu_fault pc a080cd80 ad b80003fd rw 0 mmu_idx 0 > > So it's very difficult to find LOG_UNIMP message. > > The mips_cpu_handle_mmu_fault() messages appears on enabling ANY > logging! It's not very handy. > > Adding separate log category for *_cpu_handle_mmu_fault() > logging fixes the problem. > > Signed-off-by: Antony Pavlov <address@hidden> Have you benchmarked the performance delta with this patch applied? Just boot up a random small PPC guest that shuts down immediately and "time" it with and without the patch applied. Alex
[Prev in Thread] | Current Thread | [Next in Thread] |