qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: sergey.fedorov@linaro.org
To: qemu-devel@nongnu.org
Cc: "Sergey Fedorov" <serge.fdrv@gmail.com>,
	"Richard Henderson" <rth@twiddle.net>,
	"Peter Crosthwaite" <crosthwaite.peter@gmail.com>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	"Paolo Bonzini" <pbonzini@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/8] tcg: Direct block chaining clean-up
Date: Fri, 25 Mar 2016 00:56:39 +0300	[thread overview]
Message-ID: <1458856607-3275-1-git-send-email-sergey.fedorov@linaro.org> (raw)

From: Sergey Fedorov <serge.fdrv@gmail.com>

This series combines a set of patches which is meant to improve overall code
structure and readability of direct block chaining mechanism. The other point
is to make a step towards thread safety of TB chainig.

The series' tree can be found in a public git repository [1].

[1] https://github.com/sergefdrv/qemu/tree/tb-chaining-cleanup-v2

Sergey Fedorov (8):
  tcg: Clean up direct block chaining data fields
  tcg: Use uintptr_t type for jmp_list_{next|first} fields of TB
  tcg: Rearrange tb_link_page() to avoid forward declaration
  tcg: Init TB's direct jumps before making it visible
  tcg: Clarify thread safety check in tb_add_jump()
  tcg: Rename tb_jmp_remove() to tb_remove_from_jmp_list()
  tcg: Extract removing of jumps to TB from tb_phys_invalidate()
  tcg: Clean up tb_jmp_unlink()

 include/exec/exec-all.h      |  60 +++++----
 tcg/aarch64/tcg-target.inc.c |   7 +-
 tcg/arm/tcg-target.inc.c     |   8 +-
 tcg/i386/tcg-target.inc.c    |   8 +-
 tcg/ia64/tcg-target.inc.c    |   6 +-
 tcg/mips/tcg-target.inc.c    |   8 +-
 tcg/ppc/tcg-target.inc.c     |   6 +-
 tcg/s390/tcg-target.inc.c    |  11 +-
 tcg/sparc/tcg-target.inc.c   |   9 +-
 tcg/tcg.h                    |   6 +-
 tcg/tci/tcg-target.inc.c     |  10 +-
 translate-all.c              | 292 ++++++++++++++++++++++---------------------
 12 files changed, 231 insertions(+), 200 deletions(-)

-- 
2.7.3

             reply	other threads:[~2016-03-24 21:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-24 21:56 sergey.fedorov [this message]
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 1/8] tcg: Clean up direct block chaining data fields sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 2/8] tcg: Use uintptr_t type for jmp_list_{next|first} fields of TB sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 3/8] tcg: Rearrange tb_link_page() to avoid forward declaration sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 4/8] tcg: Init TB's direct jumps before making it visible sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 5/8] tcg: Clarify thread safety check in tb_add_jump() sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 6/8] tcg: Rename tb_jmp_remove() to tb_remove_from_jmp_list() sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 7/8] tcg: Extract removing of jumps to TB from tb_phys_invalidate() sergey.fedorov
2016-03-24 21:56 ` [Qemu-devel] [PATCH v2 8/8] tcg: Clean up tb_jmp_unlink() sergey.fedorov

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=1458856607-3275-1-git-send-email-sergey.fedorov@linaro.org \
    --to=sergey.fedorov@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=crosthwaite.peter@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=serge.fdrv@gmail.com \
    /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).