All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	jani.kokkonen@huawei.com, claudio.fontana@huawei.com,
	a.rigo@virtualopensystems.com
Subject: [Qemu-devel] [RFC PATCH 0/2] Attempt to clean-up softmmu templates
Date: Fri,  8 Jan 2016 15:53:12 +0000	[thread overview]
Message-ID: <1452268394-31252-1-git-send-email-alex.bennee@linaro.org> (raw)

Hi,

While reviewing Alvise's LL/SC patches we were discussing how to avoid
duplication in some of the re-factoring work. The softmmu_template.h
code has a lot of duplication in due to BE and LE helpers. By pushing
code into an inline helper we can let the compiler do the hard work of
optimising away un-used branches but still keep broadly the same
generated code.

The VICTIM_TLB_HIT conversion was a proof of concept which only slightly
changes the code ordering in probe_write. The do_unl_store() conversion
changes a bit more as removing the goto means the code is inlined twice.
This can be fixed.

If this RFC seems a sane way to go then I can look at properly
re-factoring the code to remove duplication and maybe make the code
easier to follow and experiment with as well.

Alex Bennée (1):
  softmmu_template: add smmu_helper, convert VICTIM_TLB_HIT

Alvise Rigo (1):
  softmmu: simplify helper_*_st_name with smmu_helper(do_unl_store)

 softmmu_template.h | 150 ++++++++++++++++++++++++++++++-----------------------
 1 file changed, 85 insertions(+), 65 deletions(-)

-- 
2.6.4

             reply	other threads:[~2016-01-08 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 15:53 Alex Bennée [this message]
2016-01-08 15:53 ` [Qemu-devel] [RFC PATCH 1/2] softmmu_template: add smmu_helper, convert VICTIM_TLB_HIT Alex Bennée
2016-01-08 15:53 ` [Qemu-devel] [RFC PATCH 2/2] softmmu: simplify helper_*_st_name with smmu_helper(do_unl_store) Alex Bennée
2016-01-19 15:53   ` alvise rigo

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=1452268394-31252-1-git-send-email-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=a.rigo@virtualopensystems.com \
    --cc=claudio.fontana@huawei.com \
    --cc=jani.kokkonen@huawei.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 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.