From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Desnogues <laurent.desnogues@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QOM cast debug
Date: Thu, 20 Mar 2014 14:27:19 +0100 [thread overview]
Message-ID: <532AECB7.5070000@redhat.com> (raw)
In-Reply-To: <CABoDooM2DO4nXryFZOJpWp_TcnyFPPdGv-6=-iax0eQ2TjujMg@mail.gmail.com>
Il 20/03/2014 14:24, Laurent Desnogues ha scritto:
> On Thu, Mar 20, 2014 at 1:45 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> Il 20/03/2014 11:52, Laurent Desnogues ha scritto:
>>
>>> Hello,
>>>
>>> while looking at some perf results, I saw object_dynamic_cast_assert
>>> taking more than 3% of the run time.
>>>
>>> After some digging I found out that this time can be cut by passing
>>> --disable-qom-cast-debug to configure. This was added by Paolo:
>>>
>>> commit 3556c233d931ad5ffa46a35cb25cfc057732ebb8
>>> Author: Paolo Bonzini <pbonzini@redhat.com>
>>> Date: Fri May 10 14:16:40 2013 +0200
>>>
>>> qom: allow turning cast debugging off
>>>
>>> Cast debugging can have a substantial cost (20% or more). Instead of
>>> adding
>>> special-cased "fast casts" in the hot paths, we can just disable it in
>>> releases. The tracing facilities we just added make it easier to
>>> analyze
>>> those problems that cast debugging would reveal.
>>>
>>> I find it odd that the default is to have this debug flag on by
>>> default while the other such debug options are off. Wouldn't it make
>>> more sense to have it off by default and let devs turn it on?
>>
>>
>> I agree, but Anthony (and Andreas?) did not.
>>
>> Which path is calling object_dynamic_cast_assert so much? It was agreed to
>> just use C casts in hot code.
>
> The culprit seems to be ENV_GET_CPU:
>
> #define ENV_GET_CPU(e) CPU(arm_env_get_cpu(e))
> #define CPU(obj) OBJECT_CHECK(CPUState, (obj), TYPE_CPU)
> #define OBJECT_CHECK(type, obj, name) \
> ((type *)object_dynamic_cast_assert(OBJECT(obj), (name), \
> __FILE__, __LINE__, __func__))
>
> 0.00 0.00 1391069/289549110 io_writel [46]
> 0.00 0.00 2038947/289549110 helper_le_stl_mmu [32]
> 0.00 0.00 3986870/289549110 helper_ret_ldub_mmu [31]
> 0.00 0.00 8131587/289549110 helper_ret_ldb_cmmu [28]
> 0.00 0.00 17849223/289549110 helper_le_ldul_mmu [18]
> 0.00 0.00 32244969/289549110 tb_find_slow [26]
> 0.00 0.00 32347716/289549110
> arm_cpu_handle_mmu_fault [11]
> 0.00 0.00 32347737/289549110 get_phys_addr_v6 [17]
> 0.00 0.00 32598025/289549110 get_page_addr_code [27]
> 0.00 0.00 124705628/289549110 tb_find_fast [25]
> [106] 0.0 0.00 0.00 289549110 object_dynamic_cast_assert [106]
Andreas, why can't we just do (CPUState *) in the actual ENV_GET_CPU
macro? It's pretty much assured to be called by hot spots.
Paolo
prev parent reply other threads:[~2014-03-20 13:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 10:52 [Qemu-devel] QOM cast debug Laurent Desnogues
2014-03-20 12:45 ` Paolo Bonzini
2014-03-20 13:24 ` Laurent Desnogues
2014-03-20 13:27 ` Paolo Bonzini [this message]
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=532AECB7.5070000@redhat.com \
--to=pbonzini@redhat.com \
--cc=laurent.desnogues@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).