All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Claudio Fontana <claudio.fontana@huawei.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Jani Kokkonen <Jani.Kokkonen@huawei.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/1] tcg/aarch64: Implement tlb lookup fast path
Date: Thu, 20 Jun 2013 09:55:59 -0700	[thread overview]
Message-ID: <51C3341F.3020801@twiddle.net> (raw)
In-Reply-To: <51C3189A.5010206@huawei.com>

On 06/20/2013 07:58 AM, Claudio Fontana wrote:
>> > +    tcg_out_ldst(s, TARGET_LONG_BITS == 64 ? LDST_64 : LDST_32,
>> > +                  LDST_LD, TCG_REG_X0, TCG_REG_X2, tlb_offset & 0xfff);
>> > +    tcg_out_ldst(s, LDST_64, LDST_LD, TCG_REG_X1, TCG_REG_X2,
>> > +        (tlb_offset & 0xfff) + (offsetof(CPUTLBEntry, addend) -
>> > +             (is_read ? offsetof(CPUTLBEntry, addr_read) :
>> > +                   offsetof(CPUTLBEntry, addr_write))));
>> > +
>> > +    tcg_out_cmp(s, 1, TCG_REG_X0, TCG_REG_X3, 0);
>> > +    *label_ptr = s->code_ptr;
>> > +    tcg_out_goto_cond_noaddr(s, TCG_COND_NE);
>> > +}
> hmm should not the compare and branch actually be before the loading of the addend?
> If we jump to the slow path we don't need to load the addend do we?
> 

No, but it's the slow path, and we don't care if we do extra work.
What's more important is minimizing the memory load delay for the
fast path.


r~

  reply	other threads:[~2013-06-20 16:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-20 10:48 [Qemu-devel] [PATCH 0/1] ARM aarch64 TCG tlb fast lookup Jani Kokkonen
2013-06-20 10:53 ` [Qemu-devel] [PATCH 1/1] tcg/aarch64: Implement tlb lookup fast path Jani Kokkonen
2013-06-20 14:58   ` Claudio Fontana
2013-06-20 16:55     ` Richard Henderson [this message]
2013-06-20 17:05   ` Richard Henderson

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=51C3341F.3020801@twiddle.net \
    --to=rth@twiddle.net \
    --cc=Jani.Kokkonen@huawei.com \
    --cc=claudio.fontana@huawei.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.