From: Sergey Fedorov <serge.fdrv@gmail.com>
To: sergey.fedorov@linaro.org, qemu-devel@nongnu.org
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Richard Henderson" <rth@twiddle.net>,
"Alex Bennée" <alex.bennee@linaro.org>,
"Peter Crosthwaite" <crosthwaite.peter@gmail.com>
Subject: Re: [Qemu-devel] [PATCH 2/8] tcg: Use uintptr_t type for jmp_list_{next|first} fields of TB
Date: Thu, 24 Mar 2016 17:17:57 +0300 [thread overview]
Message-ID: <56F3F715.1080909@gmail.com> (raw)
In-Reply-To: <1458815961-31979-3-git-send-email-sergey.fedorov@linaro.org>
On 24/03/16 13:39, sergey.fedorov@linaro.org wrote:
> - * The two least significant bits of a pointer are used to choose which
> - * data field holds a pointer to the next TB:
> + * jmp_list_first and jmp_list_next are 4-byte aligned pointers to a
> + * TranslationBlock structure, and the two least significant bits of them
> + * are used to encode which data field holds a pointer to the next TB:
Maybe would be better described like this: "..., and the two least
significant bits of them are used to encode which data field of the
pointed TB should be used to traverse the list further from that TB: ..."?
Kind regards,
Sergey
> * 0 => jmp_list_next[0], 1 => jmp_list_next[1], 2 => jmp_list_first.
> * In other words, 0/1 tells which jump is used in the pointed TB,
> * and 2 means that this is a pointer back to the target TB of this list.
> */
> - struct TranslationBlock *jmp_list_next[2];
> - struct TranslationBlock *jmp_list_first;
> + uintptr_t jmp_list_next[2];
> + uintptr_t jmp_list_first;
next prev parent reply other threads:[~2016-03-24 14:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-24 10:39 [Qemu-devel] [PATCH 0/8] tcg: Direct block chaining clean-up sergey.fedorov
2016-03-24 10:39 ` [Qemu-devel] [PATCH 1/8] tcg: Clean up direct block chaining data fields sergey.fedorov
2016-03-24 13:42 ` Alex Bennée
2016-03-24 14:02 ` Sergey Fedorov
2016-03-24 15:01 ` Alex Bennée
2016-03-24 15:10 ` Sergey Fedorov
2016-03-24 15:11 ` Paolo Bonzini
2016-03-24 15:23 ` Alex Bennée
2016-03-28 22:12 ` Richard Henderson
2016-03-29 8:14 ` Paolo Bonzini
2016-03-29 8:51 ` Paolo Bonzini
2016-03-29 8:31 ` Sergey Fedorov
2016-03-29 15:37 ` Richard Henderson
2016-03-29 16:26 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2016-03-29 17:58 ` Sergey Fedorov
2016-03-24 10:39 ` [Qemu-devel] [PATCH 2/8] tcg: Use uintptr_t type for jmp_list_{next|first} fields of TB sergey.fedorov
2016-03-24 14:17 ` Sergey Fedorov [this message]
2016-03-24 14:58 ` Alex Bennée
2016-03-24 15:15 ` Sergey Fedorov
2016-03-24 10:39 ` [Qemu-devel] [PATCH 3/8] tcg: Rearrange tb_link_page() to avoid forward declaration sergey.fedorov
2016-03-24 15:04 ` Alex Bennée
2016-03-24 10:39 ` [Qemu-devel] [PATCH 4/8] tcg: Init TB's direct jumps before making it visible sergey.fedorov
2016-03-24 15:11 ` Alex Bennée
2016-03-24 15:31 ` Sergey Fedorov
2016-03-24 15:40 ` Alex Bennée
2016-03-24 15:58 ` Sergey Fedorov
2016-03-24 10:39 ` [Qemu-devel] [PATCH 5/8] tcg: Clarify "thread safaty" check in tb_add_jump() sergey.fedorov
2016-03-24 11:31 ` Paolo Bonzini
2016-03-24 12:41 ` Sergey Fedorov
2016-03-24 12:23 ` Artyom Tarasenko
2016-03-24 12:28 ` Sergey Fedorov
2016-03-24 10:39 ` [Qemu-devel] [PATCH 6/8] tcg: Rename tb_jmp_remove() to tb_remove_from_jmp_list() sergey.fedorov
2016-03-24 15:24 ` Alex Bennée
2016-03-24 10:39 ` [Qemu-devel] [PATCH 7/8] tcg: Extract removing of jumps to TB from tb_phys_invalidate() sergey.fedorov
2016-03-24 15:26 ` Alex Bennée
2016-03-24 10:39 ` [Qemu-devel] [PATCH 8/8] tcg: Clean up tb_jmp_unlink() sergey.fedorov
2016-03-24 15:36 ` Alex Bennée
2016-03-24 15:42 ` Sergey Fedorov
2016-03-24 15:52 ` Sergey Fedorov
2016-03-24 11:33 ` [Qemu-devel] [PATCH 0/8] tcg: Direct block chaining clean-up Paolo Bonzini
2016-03-24 12:21 ` 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=56F3F715.1080909@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=crosthwaite.peter@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sergey.fedorov@linaro.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).