From: Sergey Fedorov <serge.fdrv@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>,
"Sergey Fedorov" <sergey.fedorov@linaro.org>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Peter Crosthwaite <crosthwaite.peter@gmail.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH v3 05/10] tcg: Clarify thread safety check in tb_add_jump()
Date: Tue, 19 Apr 2016 15:49:55 +0300 [thread overview]
Message-ID: <57162973.1050308@gmail.com> (raw)
In-Reply-To: <87a8kpx3pq.fsf@linaro.org>
On 19/04/16 14:01, Alex Bennée wrote:
> Sergey Fedorov <sergey.fedorov@linaro.org> writes:
>
>> From: Sergey Fedorov <serge.fdrv@gmail.com>
>>
>> The check is to make sure that another thread hasn't already done the
>> same while we were outside of tb_lock. Mention this in a comment.
>>
>> Signed-off-by: Sergey Fedorov <serge.fdrv@gmail.com>
>> Signed-off-by: Sergey Fedorov <sergey.fedorov@linaro.org>
>> ---
>>
>> Changes in v2:
>> * Typo fixed in the commit title
>> * Complete rewrite of the commit body and the patch based on Paolo's comments
>>
>> include/exec/exec-all.h | 31 +++++++++++++++++--------------
>> 1 file changed, 17 insertions(+), 14 deletions(-)
>>
>> diff --git a/include/exec/exec-all.h b/include/exec/exec-all.h
>> index b055716ed690..8e81ef5fb2c2 100644
>> --- a/include/exec/exec-all.h
>> +++ b/include/exec/exec-all.h
>> @@ -391,21 +391,24 @@ static inline void tb_set_jmp_target(TranslationBlock *tb,
>> static inline void tb_add_jump(TranslationBlock *tb, int n,
>> TranslationBlock *tb_next)
>> {
>> - /* NOTE: this test is only needed for thread safety */
>> - if (!tb->jmp_list_next[n]) {
>> - qemu_log_mask_and_addr(CPU_LOG_EXEC, tb->pc,
>> - "Linking TBs %p [" TARGET_FMT_lx
>> - "] index %d -> %p [" TARGET_FMT_lx "]\n",
>> - tb->tc_ptr, tb->pc, n,
>> - tb_next->tc_ptr, tb_next->pc);
>> - /* patch the native jump address */
>> - tb_set_jmp_target(tb, n, (uintptr_t)tb_next->tc_ptr);
>> -
>> - /* add in TB jmp circular list */
>> - tb->jmp_list_next[n] = tb_next->jmp_list_first;
>> - assert(((uintptr_t)tb & 3) == 0);
>> - tb_next->jmp_list_first = (uintptr_t)tb | n;
>> + if (tb->jmp_list_next[n]) {
>> + /* Another thread has already done this while we were
>> + * outside of the lock; nothing to do in this case */
>> + return;
>> }
>> + qemu_log_mask_and_addr(CPU_LOG_EXEC, tb->pc,
>> + "Linking TBs %p [" TARGET_FMT_lx
>> + "] index %d -> %p [" TARGET_FMT_lx "]\n",
>> + tb->tc_ptr, tb->pc, n,
>> + tb_next->tc_ptr, tb_next->pc);
>> +
>> + /* patch the native jump address */
>> + tb_set_jmp_target(tb, n, (uintptr_t)tb_next->tc_ptr);
>> +
>> + /* add in TB jmp circular list */
>> + tb->jmp_list_next[n] = tb_next->jmp_list_first;
>> + assert(((uintptr_t)tb & 3) == 0);
> I think this assert can be dropped. The only call explicitly masks with
> TB_EXIT_MASK (which would be a better choice than the number 3 anyway)
> so something really strange would have had to happen in the intervening
> few lines.
What about the same assert in tb_gen_code()?
Kind regards,
Sergey
>
> Otherwise:
>
> Reviewed-by: Alex Bennée <alex.bennee@linaro.org>
>
>> + tb_next->jmp_list_first = (uintptr_t)tb | n;
>> }
>>
>> /* GETRA is the true target of the return instruction that we'll execute,
>
next prev parent reply other threads:[~2016-04-19 12:50 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 21:45 [Qemu-devel] [PATCH v3 00/10] tcg: Direct block chaining clean-up Sergey Fedorov
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 01/10] tcg: Clean up direct block chaining data fields Sergey Fedorov
2016-04-19 10:02 ` Alex Bennée
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 02/10] tcg: Use uintptr_t type for jmp_list_{next|first} fields of TB Sergey Fedorov
2016-04-19 10:34 ` Alex Bennée
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 03/10] tcg: Rearrange tb_link_page() to avoid forward declaration Sergey Fedorov
2016-04-18 17:20 ` Alex Bennée
2016-04-18 17:59 ` Sergey Fedorov
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 04/10] tcg: Init TB's direct jumps before making it visible Sergey Fedorov
2016-04-19 10:55 ` Alex Bennée
2016-04-19 12:42 ` Sergey Fedorov
2016-04-19 13:07 ` Alex Bennée
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 05/10] tcg: Clarify thread safety check in tb_add_jump() Sergey Fedorov
2016-04-19 11:01 ` Alex Bennée
2016-04-19 12:49 ` Sergey Fedorov [this message]
2016-04-19 15:27 ` Alex Bennée
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 06/10] tcg: Rename tb_jmp_remove() to tb_remove_from_jmp_list() Sergey Fedorov
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 07/10] tcg: Extract removing of jumps to TB from tb_phys_invalidate() Sergey Fedorov
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 08/10] tcg: Clean up tb_jmp_unlink() Sergey Fedorov
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 09/10] tcg: Clean up direct block chaining safety checks Sergey Fedorov
2016-04-19 11:37 ` Alex Bennée
2016-04-19 13:02 ` Sergey Fedorov
2016-04-19 14:53 ` Alex Bennée
2016-04-10 21:45 ` [Qemu-devel] [PATCH v3 10/10] tcg: Moderate direct block chaining safety checks in user mode Sergey Fedorov
2016-04-19 13:10 ` Alex Bennée
2016-04-19 13:17 ` 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=57162973.1050308@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).