qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: Re: [Qemu-devel] [PATCH] target/arm: Convert ARM_TBFLAG_* to FIELDs
Date: Mon, 17 Dec 2018 10:03:56 -0800	[thread overview]
Message-ID: <32f6ded3-4dc8-7d3f-b68b-741528433380@linaro.org> (raw)
In-Reply-To: <87k1k8gic7.fsf@linaro.org>

On 12/17/18 9:43 AM, Alex Bennée wrote:
>> Use "register" TBFLAG_ANY to indicate shared state between
>> A32 and A64, and "registers" TBFLAG_A32 & TBFLAG_A64 for
>> fields that are specific to the given cpu state.
>>
>> Move ARM_TBFLAG_BE to shared state, instead of its current
>> placement within "Bit usage when in AArch32 state".
> 
> This looks like a worthwhile clean-up but really we need to defer this
> calculation. It's in the top 2 hot functions on my build load stressor:
> 
>    5.74%  qemu-system-aarch64      [.] helper_lookup_tb_ptr
>    5.05%  qemu-system-aarch64      [.] get_phys_addr_lpae
>    4.39%  qemu-system-aarch64      [.] cpu_get_tb_cpu_state
>    3.73%  qemu-system-aarch64      [.] tcg_gen_code
>    3.65%  qemu-system-aarch64      [.] qht_lookup_custom

Yes, I know.  We need to put on our thinking caps and come up with a scheme
that minimizes the chances of missing an update to any (partially) pre-computed
value.

That has been Peter's (legitimate) resistance to such a scheme so far.  There
are a *lot* of variables that go into computing tb->flags.

In the meantime this patch just makes the task of adding bits less ugly.


r~

  reply	other threads:[~2018-12-17 18:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-14 20:18 [Qemu-devel] [PATCH] target/arm: Convert ARM_TBFLAG_* to FIELDs Richard Henderson
2018-12-17 17:43 ` Alex Bennée
2018-12-17 18:03   ` Richard Henderson [this message]
2018-12-18 15:46     ` Alex Bennée

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=32f6ded3-4dc8-7d3f-b68b-741528433380@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=peter.maydell@linaro.org \
    --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).