From: Alexander Graf <agraf@suse.de>
To: Antony Pavlov <antonynpavlov@gmail.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
Blue Swirl <blauwirbel@gmail.com>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Guan Xuetao <gxt@mprc.pku.edu.cn>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3] qemu-log: add log category for MMU info
Date: Mon, 03 Nov 2014 16:05:19 +0100 [thread overview]
Message-ID: <545799AF.4040704@suse.de> (raw)
In-Reply-To: <1414561053-29381-1-git-send-email-antonynpavlov@gmail.com>
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 <antonynpavlov@gmail.com>
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
next prev parent reply other threads:[~2014-11-03 15:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 5:37 [Qemu-devel] [PATCH v3] qemu-log: add log category for MMU info Antony Pavlov
2014-11-03 15:05 ` Alexander Graf [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-06 8:11 Antony Pavlov
2014-11-06 10:23 ` Alexander Graf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=545799AF.4040704@suse.de \
--to=agraf@suse.de \
--cc=antonynpavlov@gmail.com \
--cc=aurelien@aurel32.net \
--cc=blauwirbel@gmail.com \
--cc=edgar.iglesias@gmail.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).