[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-commits] [qemu/qemu] 339aaf: qemu-log: add log category for MMU in

From: GitHub
Subject: [Qemu-commits] [qemu/qemu] 339aaf: qemu-log: add log category for MMU info
Date: Wed, 17 Dec 2014 08:30:06 -0800

  Branch: refs/heads/master
  Home:   https://github.com/qemu/qemu
  Commit: 339aaf5b7f26d1e638641c59a44883b7654bd8ea
  Author: Antony Pavlov <address@hidden>
  Date:   2014-12-16 (Tue, 16 Dec 2014)

  Changed paths:
    M cputlb.c
    M include/qemu/log.h
    M qemu-log.c
    M target-cris/helper.c
    M target-i386/helper.c
    M target-microblaze/helper.c
    M target-mips/helper.c
    M target-ppc/mmu-hash32.c
    M target-ppc/mmu-hash64.c
    M target-ppc/mmu_helper.c
    M target-s390x/helper.c
    M target-sparc/mmu_helper.c

  Log Message:
  qemu-log: add log category for MMU info

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 appear 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>
Acked-by: Alexander Graf <address@hidden>
Reviewed-by: Richard Henderson <address@hidden>
Message-id: address@hidden
Signed-off-by: Peter Maydell <address@hidden>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]